AEM Cloud Manager stage deployment fails with OOMKilled error during UI testing
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article explains how to resolve stage deployment failures in Adobe Experience Manager Cloud Manager that are caused by OOMKilled errors during the UI Testing phase.
Description description
Environment
- Adobe Experience Manager (AEM) Cloud Manager (all versions)
Symptoms
- Stage deployment fails during the UI Testing phase.
- Deployment logs show:
waiting for container to terminate: container exited with non-zero exit code: 137, reason: OOMKilled. - The issue occurs consistently on multiple deployment attempts and always at the UI Testing stage.
Cause
The UI Testing container exceeded its allocated memory, causing the orchestrator to terminate the process with an OOMKilled (Out Of Memory Killed) error.
Resolution resolution
Follow the steps below to resolve the issue:
- Navigate to the Cloud Manager pipeline configuration for the affected environment.
- Locate the UI Testing step and increase the memory allocation to a higher value appropriate for your test suite’s requirements.
- Save the pipeline configuration changes.
- Re-run the stage deployment.
- Monitor the deployment to ensure the UI Testing phase completes successfully without OOMKilled errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles