A DevOps engineer is troubleshooting an Ansible Automation Platform deployment where ansible-navigator fails to run a playbook, showing the error 'Error: Unable to pull execution environment image'. The ansible-navigator configuration file is shown in the exhibit. Which change should the engineer make to resolve the issue?
Exhibit
Refer to the exhibit.
[root@controller ~]# cat /etc/ansible-automation-platform/ansible-navigator.yml
---
ansible-navigator:
execution-environment:
image: registry.internal.example.com/ee-supported:latest
pull:
policy: missing
playbook-artifact:
enable: false
logging:
level: debug
mode: stdout
set-environment:
ANSIBLE_INVENTORY: /opt/inventory/hosts
ANSIBLE_ROLES_PATH: /opt/rolesTrap 1: Set 'mode' to 'interactive' instead of 'stdout'
Mode affects output format, not image pulling.
Trap 2: Change the execution-environment image to…
The image name is not the cause; the error is about pulling the existing image.
Trap 3: Set 'playbook-artifact enable' to 'true'
Artifact saving does not affect image pulling.
- A
Set 'mode' to 'interactive' instead of 'stdout'
Why it fails: Mode affects output format, not image pulling.
- B
Change the execution-environment image to 'registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel8:latest'
Why it fails: The image name is not the cause; the error is about pulling the existing image.
- C
Change 'pull policy' from 'missing' to 'always'
Setting pull policy to 'always' forces ansible-navigator to fetch the execution environment image from the registry on every run, resolving the pull failure caused by a stale or missing local copy referenced by the 'missing' setting.
- D
Set 'playbook-artifact enable' to 'true'
Why it fails: Artifact saving does not affect image pulling.