[Bug 1150720] Re: [SRU] There is now a dependency on paramiko v1.8.0

[Adam Gandelman]

@ Chuck

Can you please post a better test case? I'm trying to reproduce and
verify the fix but I haven't been able to trigger the issue.   I've
followed your test case, and even gone as far as setting up remote
access to another system for cinder to create an SSH connection, but
haven't been able to trigger this on precise using  cinder-volume
2012.2.1-0ubuntu1.1~cloud (UCA) and  python-paramiko 1.7.7.1-2 (from
12.04 archive).

Also you mention this affects cinder 2012.1 (Essex) but cinder didn't
exist until 2012.2 (Folsom).

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to paramiko in Ubuntu.
https://bugs.launchpad.net/bugs/1150720

Title:
  [SRU] There is now a dependency on paramiko v1.8.0

Status in Cinder:
  In Progress
Status in Cinder folsom series:
  Fix Released
Status in “cinder” package in Ubuntu:
  Triaged
Status in “paramiko” package in Ubuntu:
  Fix Released
Status in “paramiko” source package in Precise:
  Fix Committed
Status in “paramiko” source package in Quantal:
  Triaged
Status in “cinder” source package in Raring:
  Triaged
Status in “paramiko” source package in Raring:
  Fix Released

Bug description:
  When bringing up Cinder with the storwize_svc driver, the default
  paramiko install on Power RHEL 6.3 (1.7.6) produced the following
  error when cinder-volume started:

  SSHException: Error connecting via ssh: PID check failed. RNG must be
  re-initialized after fork(). Hint: Try Random.atfork()

  Moving up to paramiko 1.9.0 fixed the issue.  We haven't diagnosed the
  root cause of the failure using 1.7.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1150720/+subscriptions