Scenario 1: Automation Hub storage issue
| Difficulty | Components | Break Type |
|---|---|---|
Easy |
Automation Hub |
Storage configuration |
Objectives
-
Verify the health of the Automation Hub pods.
-
Diagnose and resolve a storage-related failure preventing Hub from starting.
-
Understand why Automation Hub requires a ReadWriteMany (RWX) storage class.
|
Scenario 1 is different from the others. The environment is already broken at deployment. There is no Break Scenario job template to run. Log into AAP and go straight to troubleshooting. |
Troubleshooting
Step 1: Inspect Hub pods
Open the OpenShift Console and navigate to Workloads → Pods. Filter by your namespace.
Look for Hub-related pods stuck in a Pending state.
Step 2: Investigate the failure reason
Click on a failing Hub pod and review the Events tab. The error message will indicate why the pod cannot be scheduled.
Navigate to Storage → PersistentVolumeClaims and inspect the status of the Hub PVC to confirm your diagnosis.
Step 3: Fix the issue
Once you have identified the root cause, apply the fix through the OpenShift Console.
Refer to the solution page if you need guidance: Solution: Automation Hub storage issue