Troubleshoot execution environment builder

Use this reference to identify and resolve common issues when configuring or using execution environment builder in Ansible automation portal.

Common issues
Copy link

For authentication, catalog sync, and general portal issues, see Troubleshooting Ansible automation portal.

The following table lists symptoms specific to execution environment builder, their causes, and the steps to resolve them.

Expand
Symptom Cause Resolution
Execution Environments sidebar item not visible Missing ansible.execution-environments.view permission. An AAP administrator must grant the permission through RBAC. See Grant execution environment builder access. Check logs for policy check failed entries.
Collections sidebar item not visible Missing ansible.collections.view permission. An AAP administrator must grant the permission through RBAC. See Grant execution environment builder access.
Git Repositories sidebar item not visible Missing ansible.git-repositories.view permission. An AAP administrator must grant the permission through RBAC. See Grant execution environment builder access.
Saving definition files fails with "OAuth authorization failed" or HTTP 401 GitHub or GitLab OAuth token expired or OAuth App credentials missing from secrets-scm. Re-authenticate through the Git provider selector in the wizard. Verify your AAP administrator has configured OAuth credentials and uncommented the auth provider block. See Configure a GitHub App for content discovery or Set up GitLab integration. Check logs for Authentication failed for provider entries.
CI build fails with "secret not found" or "authentication required" in GitHub Actions Missing or misconfigured GitHub repository secrets. An AAP administrator must configure REGISTRY_PASSWORD, REDHAT_REGISTRY_PASSWORD, or ANSIBLE_GALAXY_SERVER_<NAME>_TOKEN on the GitHub repository or organization. See Configure a GitHub OAuth App for saving definitions, "Automated image builds". Open the failing workflow run in GitHub Actions to see which secret is missing.
Collections not appearing in wizard picker or collection catalog Content sources not configured, not synced, or sync failed. Verify with your AAP administrator that sources are configured and synced. Check logs for ansible content sync errors. If using private automation hub, verify the base URL is reachable from the portal pod.
Templates not visible on the Execution Environments Create tab Default templates unreachable, custom templates not registered, or user missing RBAC permissions.
  1. Verify the user has the required RBAC permissions to view templates. See Grant execution environment builder access.
  2. Verify the Helm chart catalog.locations entries point to accessible URLs.
  3. If using a private Git source, confirm templates have been imported. See Host EE wizard templates in a private Git repository.

Check logs for catalog processing error entries.
GitLab save succeeds but no automated build triggered Automated pipeline builds use GitHub Actions. Build the execution environment locally using ansible-builder or save the definition to a GitHub repository to trigger CI. GitLab CI support is planned for a future release.
Build fails with "collection not installable" or ansible-galaxy error Collection galaxy.yml is not at the repository root. ansible-galaxy can only install collections where galaxy.yml is at the repository root. Collections discovered at deeper crawl levels appear in the catalog but cannot be installed. See the crawlDepth note in Configure collection discovery sources.
Sync returns incomplete results or logs show HTTP 429 errors Repository provider API rate limit exhausted during content discovery. Increase schedule.frequency or reduce the number of scanned organizations. See Configure collection discovery sources.