Demystifying Ansible Automation Platform on OpenShift Container Platform
Welcome to the Lab!
Welcome to the Demystifying Ansible Automation Platform (AAP) on OpenShift Container Platform (OCP) lab!
In this lab you will troubleshoot real-world Ansible Automation Platform deployments running on OpenShift. Each scenario focuses on a different AAP component and presents a broken environment for you to diagnose and fix. No prior knowledge of the fix is expected. Your job is to observe, investigate, and reason through the problem.
Your environment
Your environment consists of a dedicated AAP instance already deployed on OpenShift. There is no bastion host. All interaction happens through:
-
The Ansible Automation Platform tab on the right side of this page.
-
The OpenShift Console accessible via the top navigation.
Your credentials
Use the following credentials to log into AAP via the tab on the right:
| Field | Value |
|---|---|
Username |
admin |
Password |
changeme |
|
The AAP tab on the right side of this page is already pointing to your AAP instance. |
OpenShift Console
The OpenShift Console is embedded and accessible via the top navigation bar. Use it to inspect pods, events, storage, and other cluster resources as you troubleshoot.
| Field | Value |
|---|---|
Username |
user-guid |
Password |
changeme |
Lab scenarios
Each scenario presents a broken AAP deployment; your goal is to identify the root cause and restore full functionality.
| Scenario | Component | Description |
|---|---|---|
1 |
Automation Hub |
Hub fails to start due to a storage configuration issue |
2 |
Automation Controller + Hub |
Wrong admin password / Database service missing |
3 |
Automation Controller + Hub |
Wrong node selector / High resource requests |
4 |
Automation Controller + Hub |
Job template with Execution Environment using wrong credentials |
5 |
Automation Hub |
Hub community sync limits / Hub sync storage issue |
6 |
Ansible Lightspeed (ALIA) |
ALIA chat assistant not responding due to wrong model configuration |
How the lab works
-
Your environment is already deployed. AAP is running on OpenShift in a namespace dedicated to you.
-
You introduce the break. For scenarios 2-6, log into AAP and run the Break Scenario job template in the Controller. This applies the failure for your scenario. For scenario 1, the environment is already broken (no action needed).
-
You investigate and fix the issue. Use the AAP UI and OpenShift Console to diagnose the problem and restore full functionality.
-
Refer to the solution page if you need guidance after attempting the diagnosis yourself.
|
You are not expected to know the fix upfront; the goal is to practice the investigation process and learn where to look in AAP on OCP. |
Navigate to your scenario using the left-hand menu to get started. Good luck!