Why Containerzed deployment is failing on the task Manage receptor firewalld port, while adding execution node to the Ansible Automation Platform?

Solution Verified - Updated -

Environment

  • Containerized Red Hat Ansible Automation Platform 2.5

Issue

  • The following error is encountered while adding an execution node to a containerized Ansible Automation Platform 2.5 installation:
TASK [ansible.containerized_installer.receptor : Manage receptor firewalld port] ********************************
fatal: [execution-aap25-kg.example.com]: FAILED! => {"changed": false, "msg": "ERROR: Exception caught: ALREADY_ENABLED: '27199:tcp' Permanent and Non-Permanent(immediate) operation"}
changed: [aap25-kg.example.com]

Resolution

  • Make sure the execution node has been added to the inventory as per the given documentation

  • Perform the following steps to open the default receptor port on the execution node:

# firewall-cmd --state
running
# firewall-cmd --add-port=27199/tcp --permanent
success
# firewall-cmd --reload
success
# firewall-cmd --list-ports27199/tcp
  • Rerun the Ansible playbook to deploy AAP.

Root Cause

  • The default port number that the receptor listens on for incoming connections from other receptor nodes is 27199. Ensure the appropriate network ports are open if a firewall is in place. For more information about the ports to open, see Container topologies, network-ports in Tested deployment models.

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