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

[Launchpad Bug Tracker]

This bug was fixed in the package paramiko - 1.7.7.1-3.1ubuntu1

---------------
paramiko (1.7.7.1-3.1ubuntu1) raring; urgency=low

  * debian/patches/fix-paramiko-rng-errors.patch: Add
    additional Random.atfork() to prevent RNG errors in large runs,
    backported from upstream git repo. (LP: #1150720)
 -- Chuck Short <zulcss at ubuntu.com>   Mon, 18 Mar 2013 12:20:43 -0500

** Changed in: paramiko (Ubuntu Raring)
       Status: Triaged => Fix Released

** Branch linked: lp:ubuntu/raring-proposed/paramiko

-- 
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” package in Ubuntu:
  Triaged
Status in “paramiko” package in Ubuntu:
  Fix Released
Status in “paramiko” source package in Precise:
  Triaged
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