$ oc get pods -A | grep -v Running | grep -v CompletedTroubleshooting the pattern
Checking the deployment status
To list pods that are not Running or Completed:
To check Argo CD application health:
$ ./pattern.sh make argo-healthcheckReviewing application logs
To check the logs of a specific application pod:
$ oc logs -n <namespace> <pod-name>Useful namespaces by variant:
ansible-automation-platform— AAP operator and instance (all variants)aap-config— CaC configuration jobsopenshift-storage— OpenShift Data Foundation (aap-with-hub,complete-aap-ao)automation-orchestrator— Automation Orchestrator and CNPG cluster (aap-with-ao,complete-aap-ao)
Retrieving credentials
If you cannot log in to AAP or Automation Orchestrator, retrieve credentials from the cluster:
$ ./pattern.sh scripts/ansible_get_credentials.sh
$ ./pattern.sh scripts/ao_get_credentials.shConfirm that secrets were loaded into Vault (./pattern.sh make load-secrets) and that External Secrets has projected them into the target namespaces.
Automation hub storage issues
If automation hub pods remain pending on aap-with-hub or complete-aap-ao, confirm that the odf Argo CD application is Healthy and that RWX storage classes from the OpenShift Data Foundation chart exist.
Hub requires RWX storage; RWO-only clusters fail to bind hub volumes.
Automation Orchestrator database issues
If Automation Orchestrator fails to start on aap-with-ao or complete-aap-ao:
Confirm the
vp-cloudnative-pg-clusterapplication is Synced and that theorchestrator-postgrescluster is ready.Confirm Vault contains
orchestrator-postgres-secret,temporal-postgres-secret, andtemporal-visibility-postgres-secretwith alphanumeric passwords.Avoid passwords that contain
@,%, or similar characters; AO builds a PostgreSQL URL that can break Alembic or configparser when those characters are percent-encoded.Remember that CloudNativePG is not supported by Red Hat for AO databases; consult the guidance here for Red Hat supported solutions.
