š” Solution: Scenario 5 ā Automation Hub sync issues
This page provides the detailed solutions for the issues presented in Scenario 5, specifically resource and storage constraints during Automation Hub synchronization.
š Problem 1: Insufficient resource limits for content pods
Diagnosis
The Automation Hub Content worker pods were being terminated (likely OOMKilled) during the resource-intensive synchronization process because the defined memory limits were too low.
š ļø Resolution: Increasing content resource limits
The fix is to increase the resource requests and limits for the Hub Content workers directly in the main Ansible Automation Platform Custom Resource (CR).
1. Update the AAP custom resource
In the OpenShift Console:
-
Navigate to Ecosystem ā Installed Operators and select your namespace.
-
Click on Ansible Automation Platform in the operator list.
-
Click the AnsibleAutomationPlatform tab and click on your AAP instance.
-
Switch to the YAML tab and modify the
spec.hub.content.resource_requirementssection:
# Example snippet of the modified AAP CR
spec:
hub:
content:
resource_requirements:
limits:
cpu: 1000m
memory: 8Gi # Increased memory is key here
requests:
cpu: 100m
memory: 200Miš Problem 2: Insufficient Persistent Volume Claim (PVC) size
Diagnosis
Synchronization failed because the PVC for file storage was too small (e.g., 25Mi), which cannot hold the repository’s contents.
š ļø Resolution: Increasing PVC storage size
The fix involves increasing the requested storage size on both the CR and the existing PVC.
1. Update the AAP custom resource (future PVCs)
Still in the AAP CR YAML view, update the Hub file storage size so future PVCs use the correct size:
# Example snippet of the modified AAP CR
spec:
hub:
file_storage_size: 10Gi # Increase this value2. Expand the existing PVC
The storage size of the existing PVC must also be increased directly, as the CR change only affects future PVCs (this requires a StorageClass that supports volume expansion; ocs-external-storagecluster-cephfs supports this).
In the OpenShift Console, navigate to Storage ā PersistentVolumeClaims and select your namespace. Find the Hub file storage PVC, open it, switch to the YAML view, change spec.resources.requests.storage to 10Gi, and click Save.