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

OpenStack Hudson 1150720 at bugs.launchpad.net
Tue Mar 19 06:42:32 UTC 2013


Reviewed:  https://review.openstack.org/24756
Committed: http://github.com/openstack/cinder/commit/db0595a4c516738f110482396e0fe90ecaf71b38
Submitter: Jenkins
Branch:    stable/folsom

commit db0595a4c516738f110482396e0fe90ecaf71b38
Author: Avishay Traeger <avishay at il.ibm.com>
Date:   Tue Mar 19 08:24:50 2013 +0200

    Backport paramiko 1.8.0 requirement to Folsom.
    
    Require paramiko >= 1.8.0
    
    There is a well-known bug in the Paramiko SSH library that causes
    these Exceptions:
    SSHException: Error connecting via ssh: PID check failed. RNG must be
    re-initialized after fork(). Hint: Try Random.atfork()
    
    This bug has been fixed in Paramiko, and therefore we should require
    the newer version for Cinder drivers that use Paramiko to function
    properly.
    
    Change-Id: Ia14b7b72393e2a2482ebde418b5477934779bf13
    Fixes: bug 1150720


** Tags added: in-stable-folsom

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