You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following error is produced when using a custom EE via Docker on MacOS, the project works fine with ansible-navigator if the EE is disabled, or with one of the two workarounds listed below. This appears to be an issue with persistent connection/control path, and permissions, and possibly ansible-navigator and ansible-builder v3 interoperability.
TASK [Gather l3_interfaces facts from the device using nxos_l3_interfaces] *****
fatal: [nxos-devnet-ao]: FAILED! => {"changed": false, "msg": "socket path /runner/.ansible/pc/46bb01b20e does not exist or cannot be found. See Troubleshooting socket path issues in the Network Debug and Troubleshooting Guide"}
I have found two workarounds:
Configure a different control_path_dir in ansible.cfg for the socket path.
If I can provide additional information, or if this is a problem with ansible-runner or ansible-builder, do let me know, and I will open an issue as needed, happy to help.
ANSIBLE-NAVIGATOR VERSION
ansible-navigator 3.5.0
CONFIGURATION
LOG FILE
STEPS TO REPRODUCE
I tried several base images, and locking ansible-core and ansible-runner versions pinned back, but the same versions do work locally, which led me to think it was related to a change in how ansible-builder v3 works, or how ansible-navigator and ansible-builder v3 work together. If I install collections locally (cisco.nxos==5.2.1) and pull creator:ee and other images built on v1 syntax, they do appear to work without any modifications or passing the root user option in.
ISSUE TYPE
SUMMARY
The following error is produced when using a custom
EE
via Docker on MacOS, the project works fine withansible-navigator
if theEE
is disabled, or with one of the two workarounds listed below. This appears to be an issue with persistent connection/control path, and permissions, and possiblyansible-navigator
andansible-builder v3
interoperability.I have found two workarounds:
control_path_dir
inansible.cfg
for the socket path.ansible-navigator.yaml
to allow--user=root
.If I can provide additional information, or if this is a problem with
ansible-runner
oransible-builder
, do let me know, and I will open an issue as needed, happy to help.ANSIBLE-NAVIGATOR VERSION
CONFIGURATION
LOG FILE
STEPS TO REPRODUCE
I tried several base images, and locking
ansible-core
andansible-runner
versions pinned back, but the same versions do work locally, which led me to think it was related to a change in howansible-builder v3
works, or howansible-navigator
andansible-builder v3
work together. If I install collections locally (cisco.nxos
==5.2.1) and pullcreator:ee
and other images built onv1
syntax, they do appear to work without any modifications or passing the root user option in.execution-environment.yml
EXPECTED RESULTS
ACTUAL RESULTS
ADDITIONAL INFORMATION
site.yml
hosts
The text was updated successfully, but these errors were encountered: