How to increase rulebook readiness timeout in Ansible Automation Platform 2.5 Containerized Environment?

Solution Verified - Updated -

Environment

  • Red Hat Ansible Automation Platform 2.5 Containerized Environment

Issue

  • EDA liveness check fails for a running activation and marked it as fails with the following error:

    2025-01-29 13:06:53,076 Activation is unresponsive. Liveness check for ansible rulebook timed out. Activation is going to be restarted.

  • When adding another rules to existing rulebook, activation fails to start with the "Activation is unresponsive" message.

  • The ansible-rulebook is slow at starting when decrypting vaulted variables and readiness check for ansible rulebook timed out.

Resolution

  • The default for the RULEBOOK_READINESS_TIMEOUT_SECONDS is 60. Increase the value of the variable to 120.

    • Login to host where EDA container is deployed

    • Edit the aap/eda/etc/settings.yaml file and add the following to the end:

      RULEBOOK_READINESS_TIMEOUT_SECONDS: 120

    • Save and exit the file

    • Run the following command to restart the EDA pods:

      # podman restart automation-eda-api automation-eda-daphne automation-eda-worker-1 automation-eda-worker-2 automation-eda-activation-worker-1 automation-eda-activation-worker-2 automation-eda-scheduler

    • Confirm at least one pod has the variable:

      # podman exec -it --user 0 automation-eda-worker-1 cat /etc/eda.yaml | grep -i readiness

Root Cause

  • The default value for the RULEBOOK_READINESS_TIMEOUT_SECONDS is 60 seconds which can lead the timeout when multiple rules are triggered within a rulebook in AAP EDA web UI.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments