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

[Adam Gandelman]

I've run through our openstack tests against quantal-proposed without
issue.

Also verified no issue with  using cinder's SSH connection pool class
and python-paramiko_1.7.7.1-3ubuntu0.1, using the following test with up
to 100 connections without issue:

import cinder.utils as utils
CONNS = 15

sshpool = utils.SSHPool('192.168.xx.xx', port=22, conn_timeout=10,
                        login='adam', password='xxx', min_size=CONNS, max_size=CONNS)
sshpool.create()

for i in range(1, CONNS):
    with sshpool.item() as ssh:
        print utils.ssh_execute(ssh, 'hostname', check_exit_code=False)

Not convinced the original issue here was ever something that affected
our Ubuntu packages to begin with.  The only reports here are reported
using RHEL 6.4 , paramiko 1.7.6 and who-knows what combination of
versions of other things in the mix (eventlet, greenlet, etc).  (Fairly
certain I was chasing another issue in comment #13)


** Tags removed: verification-needed
** Tags added: verification-done

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