[openstack-dev] [QA][Neutron] About paramiko's "SSHException: Error reading SSH protocol banner"

Yair Fried yfried at redhat.com
Fri Dec 27 05:14:56 UTC 2013

This might be completely off, in "isolated creds", a private network is created for each tenant, while the test already creates its own private tenant network, thereby changing the behavior from how it was intended to, and how it is in "simple" mode. Could this be related?
I have this patch addressing this - https://review.openstack.org/#/c/63886/
You could try and see if it makes any difference


----- Original Message -----
From: "Salvatore Orlando" <sorlando at nicira.com>
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
Sent: Friday, December 27, 2013 2:53:59 AM
Subject: [openstack-dev] [QA][Neutron] About paramiko's "SSHException: Error reading SSH protocol banner"

I put together all the patches which we prepared for making parallel testing work, and ran a few times 'check experimental' on the gate to see whether it worked or not. 

With parallel testing, the only really troubling issue are the scenario tests which require to access a VM from a floating IP, and the new patches we've squashed together in [1] should address this issue. However, the result is that timeouts are still observed but with a different message [2]. 
I'm not really familiar with it, and I've never observed it in local testing. I wonder if it just happens to be the usual problem about the target host not being reachable, or if it is something specific to paramiko. 

Any hint would be appreciated, since from the logs is appears everything is wired properly. 


[1] https://review.openstack.org/#/c/57420/ 
[2] http://logs.openstack.org/20/57420/40/experimental/check-tempest-dsvm-neutron-isolated-parallel/a74bdc8/console.html#_2013-12-26_22_51_31_817 
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

More information about the OpenStack-dev mailing list