Troubleshooting Ansible Automation Platform

Procedure

1. Log in to your cluster:

   oc login <openshift_url>

   Copy to Clipboard Toggle word wrap

2. Run one of the following commands based on your level of access in the cluster:

   • Run must-gather across the entire cluster:

     oc adm must-gather --image=registry.redhat.io/ansible-automation-platform-24/aap-must-gather-rhel8 --dest-dir <dest_dir>

     Copy to Clipboard Toggle word wrap
     • --image specifies the image that gathers data
     • --dest-dir specifies the directory for the output

   • Run must-gather for a specific namespace in the cluster:

     oc adm must-gather --image=registry.redhat.io/ansible-automation-platform-24/aap-must-gather-rhel8 --dest-dir <dest_dir> – /usr/bin/ns-gather <namespace>

     Copy to Clipboard Toggle word wrap
     • – /usr/bin/ns-gather limits the must-gather data collection to a specified namespace

3. To attach the must-gather archive to your support case, create a compressed file from the must-gather directory created before and attach it to your support case.

   • For example, on a computer that uses a Linux operating system, run the following command, replacing <must-gather-local.5421342344627712289/> with the must-gather directory name:

     $ tar cvaf must-gather.tar.gz <must-gather.local.5421342344627712289/>

     Copy to Clipboard Toggle word wrap

Procedure

1. Change the /etc/pulp/settings.py file on private automation hub and add one of the following parameters depending on your configuration:

   • Single controller

     CONNECTED_ANSIBLE_CONTROLLERS = ['<https://my.controller.node>']

     Copy to Clipboard Toggle word wrap

   • Many controllers behind a load balancer

     CONNECTED_ANSIBLE_CONTROLLERS = ['<https://my.controller.loadbalancer>']

     Copy to Clipboard Toggle word wrap

   • Many controllers without a load balancer

     CONNECTED_ANSIBLE_CONTROLLERS = ['<https://my.controller.node1>', '<https://my.controller2.node2>']

     Copy to Clipboard Toggle word wrap

2. Stop all of the private automation hub services:

   # systemctl stop pulpcore.service pulpcore-api.service pulpcore-content.service pulpcore-worker@1.service pulpcore-worker@2.service nginx.service redis.service

   Copy to Clipboard Toggle word wrap

3. Restart all of the private automation hub services:

   # systemctl start pulpcore.service pulpcore-api.service pulpcore-content.service pulpcore-worker@1.service pulpcore-worker@2.service nginx.service redis.service

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a collections folder inside of the project repository.

2. Add a requirements.yml file inside of the collections folder and add the collection:

   collections:
   - <collection_name>

   Copy to Clipboard Toggle word wrap

1. Go to automation controller.
2. From the navigation panel, select Settings → Jobs settings.

3. Under Extra Environment Variables add the following:

   {
   "ANSIBLE_TIMEOUT": 60
   }

   Copy to Clipboard Toggle word wrap

1. Run the following commands to list all of the pending jobs:

   # awx-manage shell_plus

   Copy to Clipboard Toggle word wrap

   >>> UnifiedJob.objects.filter(status='pending')

   Copy to Clipboard Toggle word wrap

2. Run the following command to cancel all of the pending jobs:

   >>> UnifiedJob.objects.filter(status='pending').update(status='canceled')

   Copy to Clipboard Toggle word wrap

Procedure

1. Go to automation controller.
2. From the navigation panel, select Administration → Execution Environments.
3. Click the execution environment assigned to the job template that is failing.
4. Click Edit.
5. Assign the appropriate Registry credential from your private automation hub to the execution environment.

Procedure

1. In all controller and hybrid nodes, run the following commands to create a file called custom.py:

   # touch /etc/tower/conf.d/custom.py

   Copy to Clipboard Toggle word wrap

   # chmod 640 /etc/tower/conf.d/custom.py

   Copy to Clipboard Toggle word wrap

   # chown root:awx /etc/tower/conf.d/custom.py

   Copy to Clipboard Toggle word wrap

2. Add the following to the /etc/tower/conf.d/custom.py file:

   DEFAULT_CONTAINER_RUN_OPTIONS = ['--network', 'slirp4netns:enable_ipv6=true,cidr=192.0.2.0/24']

   Copy to Clipboard Toggle word wrap
   • 192.0.2.0/24 is the value for the new CIDR in this example.

3. Stop and start the automation controller service in all controller and hybrid nodes:

   # automation-controller-service stop

   Copy to Clipboard Toggle word wrap

   # automation-controller-service start

   Copy to Clipboard Toggle word wrap

   All containers will start on the new CIDR.