For those having paramiko issues, I can't reproduce, but please try this...

Archives Ansible Project
1

Explanation -- the paramiko error says please try to run
"Random.atfork()" which is a pyCrypto thing. It seems to be a newer
Pycrypto issue (CentOS 6 does not have this function, it seems), not
even a paramiko bug at all. Given it seems to be related to forking,
I'd like to know if this works, if not, it may be a starting point for
something that does actually work with the paramiko issue.

I have attached a patch I would like you to test.

BTW, here's the part of the PyCrypto code that is being annoying:

  def _check_pid(self):
        # Lame fork detection to remind developers to invoke Random.atfork()
        # after every call to os.fork(). Note that this check is not reliable,
        # since process IDs can be reused on most operating systems.

2

I went ahead and pushed this attempted fix for those using git, we can back it off it proves not useful.

It seems like a pycrypto slash paramiko mismatch, more or less, so a newest paramiko should do the right thing. I’ve heard people say this does NOT fix the problem though, hence this attempted workaround.

Anyhow, let me know…

–Michael

3

For the record, this fix works for me, on Ubuntu Oneiric (11.10) with latest Paramiko (1.7.7.1).