Posted on July 6, 2016 1:56 pm
 |  Asked by Albert Pang
 |  777 views
0
0
Print Friendly, PDF & Email

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?

Thanks.

Albert.

0
Posted by Philip DiLeo
Answered on July 6, 2016 2:02 pm

Hi Albert,

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.
0
Posted by Albert Pang
Answered on July 6, 2016 3:55 pm

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?

Thanks.

Hi All,
just to echo Alberts thoughts/concerns/questions around documentation; and i’m aware this takes a lot of time and effort.
I would agree and appreciate a clean separation of notes,instructions etc between the old and new methods.
I think there’s possibly a lack of clarity, unfortunately, that clearly defines the new methodology;which appears to have great benefits .
just my 2 cents as they say

regards

Rich

(Richard Botham Botham at July 20, 2016 10:15 pm)

Hi Richard,
We apologize that the transition between solutions took some time to hammer out. Now, you’ll notice a few things:

– The Arista.eos role has been deprecated. This is documented in the README as well as in the ReadtheDocs.
– Some articles have been written to describe the updated solution right here at EOS Central:

https://eos.arista.com/arista-ansible-a-dramatically-simple-new-approach (high-level intro)
https://eos.arista.com/arista-ansible-getting-started (getting started)
https://eos.arista.com/arista-eos-roles-for-ansible (advanced usage)

Hopefully these can help!

(Philip DiLeo at September 6, 2016 2:02 pm)

Post your Answer

You must be logged in to post an answer.