AEM Cloud Manager deployment pipeline stuck during deployment
This article explains how to troubleshoot an Adobe Experience Manager (AEM) as a Cloud Service deployment pipeline that remains in a running or blocked state during Build or deployment. The logs can identify invalid Oak index definitions, FileVault package validation failures, custom code errors, or Publish-container readiness problems. To resolve the issue, review the pipeline and deployment logs, correct the code or configuration when the logs identify a customer issue, validate the package locally, rerun the pipeline, and verify that the environment and pods become healthy.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Adobe Experience Manager Cloud Manager
- Cloud Manager deployment pipeline
- Custom Oak index and FileVault package definitions in the project codebase
- Publish environment undergoing deployment and readiness checks
Issue/Symptoms
- When you run a Cloud Manager deployment, the pipeline remains in a running state during Build or Deploy to Stage and doesn’t progress.
- The blocked pipeline prevents release activity and promotion to higher environments.
- Build logs contain errors such as ValidationViolation: Mandatory child node missing or invalid node-type errors in configuration files.
- Publish containers start but don’t become ready, so the environment doesn’t reach the required readiness state.
Cause
The pipeline doesn’t progress when Build or deployment validation rejects an invalid Oak index definition, a missing mandatory child node, or an invalid node type in a FileVault package. A separate deployment-readiness condition occurs when Publish containers start but don’t become ready, so Cloud Manager can’t mark the environment as ready. The relevant cause is determined from the pipeline and deployment logs.
Resolution resolution
Follow the steps below to resolve the issue:
-
Review the Cloud Manager pipeline execution details for the affected run.
-
Download and review the build and deployment logs, focusing on the Build and Deploy steps.
-
Look for Oak index or FileVault package-validation errors, such as:
- ValidationViolation: Mandatory child node missing
- Invalid node-type errors in configuration files, such as
src/main/content/jcr_root/_oak_index/your-index-name/config.xml.
-
Update the Oak index configuration files in your project codebase so they comply with AEM as a Cloud Service indexing rules and JCR/Oak node types. Note: Deploy Oak index definitions as code through Cloud Manager. Don’t manually modify runtime index nodes in a running environment.
-
Run the FileVault Package Validator locally against your package before committing the changes. Confirm that the package definitions pass validation.
-
After correcting the configuration issues, start a new pipeline execution in Cloud Manager.
-
Monitor the pipeline and confirm that it progresses beyond the previously blocked step.
-
If the Publish tier remains in Progressing with containers not ready:
- Review the deployment logs for container-startup errors.
- Address the runtime errors or misconfigurations identified in the logs.
Note: If the logs don’t identify a customer code or configuration problem and the containers remain not ready, collect the Cloud Manager and deployment logs and contact Adobe Support. Don’t attempt to manage the AEM pods directly.
-
Verify that the deployment pipeline completes successfully and that all pods are reported as healthy in Cloud Manager.