Chapter 13. Troubleshooting the Red Hat Ansible Automation Platform Operator on OpenShift Container Platform

Procedure

1. Log in to the OpenShift Container Platform web console.
2. In the navigation menu, select Home Events.
3. Select your project from the project list.
4. To view events for a specific resource, navigate to that resource’s page. Many resource pages, such as pods and deployments, have their own Events tab.
5. Select a resource to bring you to the Pod Details page.

Procedure

1. To find the pod name, run:

   oc get pods | grep operator

   Copy to Clipboard Toggle word wrap

2. to view the logs for the pod, run:

   oc logs <operator-pod-name> -f

   Copy to Clipboard Toggle word wrap

   1. Alternatively, to view the logs without first getting the pod name, run:

      oc logs deployments/automation-controller-operator-controller-manager -c automation-controller-manager -f

      Copy to Clipboard Toggle word wrap

Procedure

1. Edit the automation controller CR and set the no_log field to false in the spec.

   apiVersion: automationcontroller.ansible.com/v1beta1
   kind: AutomationController
   metadata:
     name: controller-demo
   spec:
     no_log: false

   Copy to Clipboard Toggle word wrap
   Note

   This might expose sensitive data in the logs. On production clusters, this value must generally be set to true unless you are actively debugging an issue.

2. To increase the Ansible Playbook verbosity from the operator, set the verbosity level using an annotation:

   annotations:
       ansible.sdk.operatorframework.io/verbosity: "4"

   Copy to Clipboard Toggle word wrap

Procedure

1. To view a human-readable summary of a resource, run:

   oc describe -n <namespace> <resource> <resource-name>

   Copy to Clipboard Toggle word wrap

2. To view the complete YAML definition of a resource, use the -o yaml flag:

   oc get -n <namespace> <resource> <resource-name> -o yaml

   Copy to Clipboard Toggle word wrap

   • For example, to get the YAML for the automationcontroller custom resource, run:

     oc get -n aap automationcontroller aap -o yaml

     Copy to Clipboard Toggle word wrap

Procedure

1. To see all available configuration parameters for a top-level CR, run:

   oc explain ansibleautomationplatform.spec

   Copy to Clipboard Toggle word wrap

2. To view specific nested sections, query them directly:

   oc explain automationcontroller.spec.postgres_configuration_secret
   oc explain automationcontroller.spec.route_tls_termination_mechanism

   Copy to Clipboard Toggle word wrap

3. To explore all nested fields at once, use the --recursive flag:

   oc explain automationcontroller.spec --recursive

   Copy to Clipboard Toggle word wrap

Procedure

1. To start the must-gather tool, run:

   oc adm must-gather --image=registry.redhat.io/ansible-automation-platform-25/aap-must-gather-rhel8

   Copy to Clipboard Toggle word wrap
   Note

   For version 2.6, the base image name changes to registry.redhat.io/ansible-automation-platform-26/aap-must-gather-rhel9.

2. View the collected data, use the omc tool to query the must-gather tarball as if it were a live cluster.

   omc use <path-to-must-gather>
   omc get pods

   Copy to Clipboard Toggle word wrap