At Fri, 27 Dec 2013 01:53:59 +0100, Salvatore Orlando wrote: > > [1 <multipart/alternative (7bit)>] > [1.1 <text/plain; ISO-8859-1 (7bit)>] > 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. It seems that a TCP connection has been established but paramiko failed get data from the server in time. Does increasing paramiko timeout help? > [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 > [1.2 <text/html; ISO-8859-1 (quoted-printable)>] > > [2 <text/plain; us-ascii (7bit)>] > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev