Scenario 5: Automation Hub sync issues

Difficulty Components Break Type

Easy

Automation Hub

Repository synchronization

Objectives

  • Log in to the AAP Gateway UI successfully.

  • Navigate to Automation Content → Repositories.

  • Attempt to synchronize the built-in Community repository.

  • Diagnose and resolve the 2 underlying issues preventing successful synchronization.

Troubleshooting

Step 1: Run the Break Scenario job

Log into AAP using the Ansible Automation Platform tab. Navigate to Automation Execution → Templates and launch the Break Scenario job template. Wait for it to complete before proceeding.

Step 2: Attempt a repository sync

In the AAP UI, navigate to Automation Content → Repositories. Find the Community repository and trigger a sync. Observe the result.

Step 3: Inspect Hub pod logs

Open the OpenShift Console and navigate to Workloads → Pods. Filter by your namespace.

Identify the relevant Hub pods and review their Logs tab for errors related to the sync failure.

Step 4: Fix the issues

Once you have identified the root causes, apply the fixes.

Refer to the solution page if needed: Solution: Automation Hub Sync Issues

Step 5: Verify

After applying the fixes, attempt to sync the Community repository again. A successful synchronization job confirms the scenario is resolved.

Hint

There are 2 issues. The first error message may not immediately reveal the root cause; search for the specific error text to find relevant Red Hat Knowledge Base articles. Once the first issue is resolved, the second one will become apparent from the next sync attempt.