-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ansible 2.9.4 does not work, DNE code must be run on Ansible 2.5.4 #98
Comments
@kiskander Can you take a look at the dCloud Pod and see if the code/Ansible setup needs to change to avoid this error on Ansible's latest version? |
Pasting in the content of the zip file for review. Shows the "invalid connection specified, expected connection=local, got network_cli"} message:
|
annegentle
changed the title
Ansible does not work
Ansible 2.9.4 does not work, DNE code must be run on Ansible 2.5.4
Mar 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
We have delivered DevNet Express training. Everything worked fine, except IOS-XE config management with Ansible. It worked perfectly during the dry runs, but not during the real event. I realized that Ansible version (what PIP installs) was upgraded from 2.5.4 to 2.9.4.
In summary, dry run worked fine with 2.5.4, but it failed with 2.9.4.
DevNetNotes_Ansible.zip
Attached file shows the problems. IOS Modules produced a different error ("invalid connection specified, expected connection=local, got network_cli"}
) than Netconf Module (msg": "Privilege escalation method not found: enable").
Ansible ran on the CentOS workstation of the PoD, not on local machines.
The text was updated successfully, but these errors were encountered: