-
Notifications
You must be signed in to change notification settings - Fork 663
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
RuntimeError: You must install paramiko package (pip install paramiko) to use the paramiko backend [Molecule verify, Ansible 2.8, Testinfra 3.x, AWS EC2 driver] #2070
Comments
Righhhhhht, thanks for this bug report! I was also seeing this in previous CI build logs and had no idea where to start looking. This makes sense and I'll try to dig into fixing this ASAP. |
Perhaps #2069 is related ... |
OK, I've given this a stab at #2076. |
Same issue with Google GCE driver (jonashackt/molecule-ansible-google-cloud#2, build log: https://travis-ci.org/jonashackt/molecule-ansible-google-cloud/builds/545286129), but I guess #2076 will fix that too :) Waiting for 2.22 final release 🤙 |
Issue Type
Molecule and Ansible details
Prerequisites (install testinfra first to fix #1727)
Molecule installation method (one of):
Ansible installation method (one of):
Detail any linters or test runners used:
Desired Behavior
molecule verify --scenario-name aws-ec2-ubuntu
should verify a AWS EC2 instance (like it does with Ansible 2.7.x and Testinfra 2.x)Actual Behaviour
See build log https://circleci.com/gh/jonashackt/molecule-ansible-docker-vagrant/26
Seems that
paramiko
is now optional from Ansible 2.8.x on (see https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst and look forparamiko
).Installing paramiko manually before the Molecule execution, the
molecule verify
step failes withparamiko.ssh_exception.AuthenticationException: Authentication failed.
(see build log https://circleci.com/gh/jonashackt/molecule-ansible-docker-vagrant/27) or details here:Full documentation here: https://github.com/jonashackt/molecule-ansible-docker-vagrant/issues/3
The text was updated successfully, but these errors were encountered: