Documentation

Pipeline fails at build step due to ACL set on non-existent path

Last update: Mon Jun 17 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Learn how to solve the issue where pipeline fails at build step due to Access Control Lists (ACL) set on non-existent path by configuring the repo init scripts.

Description description

Environment

  • Adobe Experience Manager

  • AEM Cloud Manager

Issue/Symptoms

Pipeline fails at build step due to ACL set on non-existent path.

Steps to reproduce:

  1. Log in to the Cloud Manager.
  2. Download the build log under Build Images for the production pipeline and check for errors.
  3. The following error message occurs for the Build Image step:  Cannot set ACL on non-existent path /content/< wknd> /us/en/dealer.

Resolution resolution

  1. Create a path with the correct node type in the same repo init script where you are trying to set Access Control Lists (ACLs).
  2. Redeploy.
  3. You should see a message in the Cloud Manager that shows the build is complete.

For detailed steps on how to configure the repo init scripts, refer to Repository-initialization in Apache documentation.

Cause

Repo init scripts can fail for a number of reasons. One possible reason is that the path before the ACL permissions were not set at first, or an action is being performed on a non-existing path.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f