ansible testserver -m ping -vvvv: FAILED => SSH Error: debug1: Calling cleanup 0x8078582(0x0)

Archives Ansible Project
41

VirtualBox

42

Brain, I’ve made OpenIndiana Vagrant boxes available for you to ease the reproduction of the bug:

43

Having issues with vagrant, the "vagrant init dusank/oi-desktop
--provider virtualbox" suggested on the site returns as an 'invalid
option'
and trying to download the box directly gives me an 'unrecognized
format' error. Probably a versions issue, looking into that.

44

Just leave out the “–provider virtualbox” argument. It does not seem to work and virtualbox is the default provider anyhow.

45

You just run the command, it creates a Vagrantfile, then you can run vagrant up which downloads the box if it is not cached already.

46

if i do that it cannot find the box

47

if i add the full url i get the invalid format, not sure what is going on

48

is there a way for me to download the image directly, I will probably
get it done faster than debugging vagrant.

49

Simply running vagrant init dusank/oi-server or vagrant init dusank/oi-desktop works for me with Vagrant 1.7.2.

I am not aware of any other way to download the boxes.

50

You can try downloading from https://atlas.hashicorp.com/dusank/boxes/oi-server/versions/2015.05/providers/virtualbox.box or https://atlas.hashicorp.com/dusank/boxes/oi-desktop/versions/2015.05/providers/virtualbox.box and then renaming/moving the hc-download file.

51

Brian, have you been finally able to reproduce the bug?

52

downloaded, but not tested, I have not had the time yet.

53

Brian, when do you think you’ll find enough time to look into it?

54

Ok, i think i found the issue, Sun ssh does not like control master,
on my 'test machines' i had paramiko as the default connection.

I had made it part of my initialization at one point and completely
forgot about it (hidden in my 'Solaris-family' ansible.cfg. So you
can either override the ssh args in the ansible.cfg or just switch to
using paramiko (I suggest the latter as it will perform better than
Sun ssh).

55

Thanks Brian, that is great news!

Does Ansible not use paramiko by default? At least that is how I understood the paramiko section here http://docs.ansible.com/glossary.html

Can you please tell me what exactly I should put into ansible.cfg to make this switch to paramiko use happen?

=Dusan

56

Does Ansible not use paramiko by default? At least that is how I understood the paramiko section here http://docs.ansible.com/glossary.html

Can you please tell me what exactly I should put into ansible.cfg to make this switch to paramiko use happen?

Hi Dusan,

have a look at the ssh (native) section on that page, ansible will use
OpenSSH as default, when that one is “sufficiently new” as these
support ControlMaster and ControlPersist settings. I guess paramiko does
not support them.

Regards,
Marcus

57

Thanks Marcus, that clears things up for me. The documentation could be improved a bit on this, to at least reference the Connection Type section from the paramiko one to avoid confusion.

58

Can someone please point me to the manual page for the ansible command?

I figured out by way of guessing that adding “-c paramiko” does the trick (it finally works for me), yet I would still like to read the documentation on the command and somehow cant find it.

And last but not least many thanks to Brian for his time, patience and great support!

59

set transport = paramiko in ansible.cfg. The default 'smart' tries to
use the local ssh if the version is new enough (does not factor Sun
ssh in) and fallbacks on paramiko otherwise. I'll make a note to try
to also use paramiko in the case of Sun ssh.