Chapter 8. Rulebook activations troubleshooting

Procedure

1. Confirm whether there are other running activations and if you have reached the limits (for example, memory or CPU limits).

   1. If there are other activations running, terminate one or more of them, if possible.
   2. If not, check that the default worker, Redis, and activation worker are all running.
   3. If all systems are working as expected, check your eda-server internal logs in the worker, scheduler, API, and nginx containers and services to see if the problem can be determined. These logs reveal the source of the issue, such as an exception thrown by the code, a runtime error with network issues, or an error with the rulebook code. If your internal logs do not provide information that leads to resolution, report the issue to Red Hat support.

Procedure

1. Log in to Ansible Automation Platform.
2. From the navigation panel, select Automation Decisions Rulebook Activations.
3. From the Rulebook Activations page, select the activation in your list that keeps restarting. The Details page is displayed.
4. Click the History tab for more information and select the rulebook activation that keeps restarting. The Details tab is displayed and shows the output information.

5. Check the Restart policy field for your activation.

   There are three selections available: On failure (restarts a rulebook activation when the container process fails), Always (always restarts regardless of success or failure with no more than 5 restarts), or Never (never restarts when the container process ends).

   1. Confirm that your rulebook activation Restart policy is set to On failure. This is an indication that an issue is causing it to fail.
   2. To possibly diagnose the problem, check the YAML code and the instance logs of the rulebook activation for errors.
   3. If you cannot find a solution with the restart policy values, proceed to the next steps related to the Log level.

6. Check your log level for your activation.

   1. If your default log level is Error, go back to the Rulebook Activation page and recreate your activation following procedures in Setting up rulebook a activation.
   2. Change the Log level to Debug.
   3. Run the activation again and navigate to the History tab from the activation details page.
   4. On the History page, click one of your recent activations and view the Output.

Procedure

1. Check the rulebook source: Review the source plugin defined in your rulebook YAML (for example, ansible.eda.webhook, ansible.eda.kafka).
2. Verify event input: Confirm that the events you are sending to Event-Driven Ansible controller are compatible with the source plugin defined in the rulebook. If the rulebook expects a Kafka message, it cannot process a generic webhook event.
3. Confirm activation mapping: If you are using event streams, ensure the correct event stream is mapped to the rulebook during the activation setup. A mismatch here will result in the activation receiving no data.

Procedure

1. Check rule conditions: Review the rulebook YAML to confirm that the conditions (the when statements) are accurately written and precisely match the structure and values of the incoming event payload.
2. Verify indentation and syntax: Ensure all rulebook syntax and indentation are correct, as a simple error can prevent the rule engine from evaluating conditions.
3. Validate actions: Confirm that the specified action is a recognized and correctly configured action (for example, run_job_template with the proper arguments).

Procedure

1. To help resolve the issue, confirm that you have set up a Red Hat Ansible Automation Platform credential and have obtained the correct automation controller URL.

   1. If you have not set up a Red Hat Ansible Automation Platform credential, follow the procedures in Setting up a Red Hat Ansible Automation Platform credential. Ensure that this credential has the host set to the following URL format: https://<your_gateway>/api/controller
   2. When you have completed this process, try setting up your rulebook activation again.