[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-3ubuntu0.1

---------------
paramiko (1.7.7.1-3ubuntu0.1) quantal-proposed; 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)
 -- Adam Gandelman <adamg at ubuntu.com>   Wed, 05 Jun 2013 10:55:10 -0700

** Changed in: paramiko (Ubuntu Quantal)
       Status: Fix Committed => Fix Released

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-1664

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