On Automation Controller, Jobs are failing with error "Bad owner or permissions on /etc/ssh/ssh_config.d/05-redhat.conf"

Solution Verified - Updated -

Environment

  • Red Hat Ansible Automation Platform 2.x

Issue

  • On Automation Controller, Jobs are failing with the error "Bad owner or permissions on /etc/ssh/ssh_config.d/05-redhat.conf"

  • Ad-hoc commands are failing with the following error.

         "changed": false,
    "msg": "Failed to connect to the host via ssh: OpenSSH_8.0p1, OpenSSL 1.1.1k  FIPS 25 Mar 2021\\r\\ndebug1: Reading configuration data /etc/ssh/ssh_config\\r\\ndebug3: /etc/ssh/ssh_config line 52: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0\\r\\nBad owner or permissions on /etc/ssh/ssh_config.d/05-redhat.conf",
    "unreachable": true
}

Resolution

  • Stop the Red Hat Ansible Automation Platform services.

    # automation-controller-service stop

  • Switch to awx user and reset the podman.

    # su - awx
# podman system reset

  • If the Controller system has access to the internet, download the images using the following commands.

    # podman pull registry.redhat.io/ansible-automation-platform-24/ee-supported-rhel8
# podman pull registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel8
# podman pull registry.redhat.io/ansible-automation-platform-24/ansible-builder-rhel8

  • If the system does not have access to the internet, then copy the images from the bundle installer and load them into the podman using awx user.

    • Copy the bundle/images directory from the Ansible Automation Platform Bundle installer to /var/lib/awx as root user

    • Change the ownership of the directory to awx.

      # chown -R awx:awx /var/lib/awx/images

    • Load the images in podman using awx user.

      # su - awx
# cd images
# podman load -i ee-supported-rhel8.tgz
# podman load -i ee-minimal-rhel8.tgz
# podman load -i ansible-builder-rhel8.tgz

  • Start the services.

    # automation-controller-service start

Root Cause

  • Due to some reasons, the images loaded in the podman gets corrupted, resulting in the reported issue.

Diagnostic Steps

  • Ansible jobs fail with the following error.

    <node1.example.com> (255, b'', b'OpenSSH_8.0p1, OpenSSL 1.1.1k  FIPS 25 Mar 2021\\r\\ndebug1: Reading configuration data /etc/ssh/ssh_config\\r\\ndebug3: /etc/ssh/ssh_config line 52: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0\\r\\nBad owner or permissions on /etc/ssh/ssh_config.d/05-redhat.conf\\r\\n')
node1.example.com | UNREACHABLE! => {
     "changed": false,
    "msg": "Failed to connect to the host via ssh: OpenSSH_8.0p1, OpenSSL 1.1.1k  FIPS 25 Mar 2021\\r\\ndebug1: Reading configuration data /etc/ssh/ssh_config\\r\\ndebug3: /etc/ssh/ssh_config line 52: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0\\r\\nBad owner or permissions on /etc/ssh/ssh_config.d/05-redhat.conf",
    "unreachable": true
}

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