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

Chuck Short chuck.short at canonical.com
Mon Mar 18 18:11:26 UTC 2013


[Impact] When starting cinder-volume  version 2012.1 on 12.04, cinder-
volume will give an error and exit:

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

[Test Case]

1. Install 2012.1 on 12.04 from the Ubuntu Cloud Archive
2. Activate the storwize_svc driver
3. Start cinder-volume
4. Observe the exception when starting cinder-volume

[Regression Potential]

None

-- 
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




More information about the foundations-bugs mailing list