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

James Page james.page at ubuntu.com
Wed Mar 13 14:37:39 UTC 2013


Raising a distro task for Ubuntu; its to late to upgrade paramiko for
13.04 so we will have to cherry pick a fix to support this (and patch
out the 1.9.0 requirement in cinder packaging).

** Also affects: paramiko (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: paramiko (Ubuntu Raring)
   Importance: Undecided
       Status: New

** Changed in: paramiko (Ubuntu Raring)
   Importance: Undecided => High

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

-- 
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:
  There is now a dependency on paramiko v1.9.0

Status in Cinder:
  In Progress
Status in “cinder” package in Ubuntu:
  Triaged
Status in “paramiko” package in Ubuntu:
  Triaged
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:
  Triaged

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




More information about the foundations-bugs mailing list