AEM as a Cloud Service Dev pipeline failure due to RepoInit ACL on non-existent path
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article describes how to address failures in the AEM as a Cloud Service Dev pipeline during the PREPARE_CONTENT/author step when a RepoInit ACL statement references a path that does not exist.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Dev pipeline in Cloud Manager
Symptoms
The Dev pipeline fails consistently during the PREPARE_CONTENT/author step in the image build phase. Logs show an error similar to:
Failed to set ACL (javax.jcr.PathNotFoundException: Cannot set ACL on non-existent path /apps/dam/gui/content/assets/jcr:content/mimeTypeLookup)
A custom RepoInit block attempts to set an ACL for a service user on this non-existent path. This block is present in failing builds but was not present in the last successful build. The issue is not related to an AEM release change.
Cause
The pipeline fails because a RepoInit ACL statement targets a non-existent path under /apps, resulting in a javax.jcr.PathNotFoundException. The Asset Share Commons package typically grants access under /libs, so the additional /apps ACL is unnecessary unless a custom overlay exists.
Resolution resolution
Follow the steps below to resolve the issue.
- Locate the custom RepoInit configuration in your codebase, especially in ui.config or Asset Share-related modules. Look for files named like org.apache.sling.jcr.repoinit.RepositoryInitializer *.cfg.json or .config files containing the problematic RepoInit block.
- Review the RepoInit block and identify any statements attempting to set ACLs on /apps/dam/gui/content/assets/jcr:content/mimeTypeLookup.
- Remove the ACL statement targeting this path if there is no intentional overlay at /apps/dam/gui/content/assets/jcr:content/mimeTypeLookup.
- If an overlay is required, ensure the path exists in your ui.apps package and is deployed before the RepoInit is executed.
- Commit and redeploy the changes to the pipeline.
- Monitor the PREPARE_CONTENT/author step for successful completion.