My company has been using Ansible to configure our Arista switches. We were using Ansible 1.8 with the ‘arista.eos’ role. We have now upgraded to Ansible 2.2 have started to migrate our ansible-playbook to use the built-in role (e.g. eos_config). However, we have ran into a very basic problem.
Running ansible-playbook with ‘-vvvv’ flag, I’m getting the following error msg:
“paramiko is required but does not appear to be installed”
I have verified that paramiko is indeed installed on my host running ansible-playbook.
Do I have to install it on the Arista switch as well? (pip list on EOS Bash Shell does not show that it’s installed).
Anyone else running into this issue?
Just responded on the ansible-dev alias but I’ll paste it here for any others that may run into this issue.
- Confirm you are using ’connection:local’ in your playbook. With the new modules all modules are executed locally. Even when you use transport: cli, the ssh connection is actually created from a local module.
- What version of paramiko in installed? I’ve hit issues with paramiko 2.0.0 and OSX.
Thanks for the response.
No, I was not using connection:local. I was using the ’ansible’ user set-up in EOS bash shell as per ’old’ instructions pre 2.1. You mean that I should be using a CLI user e.g.
username XXXX role network-admin secret 5 xXXXXXXXX
how about enable password?
I am using paramiko 2.0.1 running from Ubuntu 14.04 with Python 2.7.6.
I tried to change it to connection:local, but I’m getting lots of error (parse error) when the setup.py is run.
Looks like that I’m mixing the pre 2.1 and post 2.1 instructions. Do you have a clean set of instructions for setting this up?
– The Arista.eos role has been deprecated. This is documented in the README as well as in the ReadtheDocs.
https://eos.arista.com/arista-ansible-a-dramatically-simple-new-approach (high-level intro)
Hopefully these can help!
Post your Answer
You must be logged in to post an answer.