Occasionally, SSH will get wedged so that a connection attempt is stuck
forever. When this happens, we need Tempest to abort the attempt and try
again. Currently, the individual connection timeout is set to the
overall timeout, so there will only ever be one attempt if this happens.
Using the channel_timeout instead will ensure that multiple connection
attempts are made even when the connection is wedged.
Reviewed: https:/ /review. openstack. org/72468 /git.openstack. org/cgit/ openstack/ tempest/ commit/ ?id=50eaa8c8018 9d0c938f2dbced7 0df4d14dc2cdfa
Committed: https:/
Submitter: Jenkins
Branch: stable/havana
commit 50eaa8c80189d0c 938f2dbced70df4 d14dc2cdfa
Author: Soren Hansen <email address hidden>
Date: Wed Nov 27 14:39:28 2013 +0100
Use channel_timeout for SSH connection timeout
Occasionally, SSH will get wedged so that a connection attempt is stuck
forever. When this happens, we need Tempest to abort the attempt and try
again. Currently, the individual connection timeout is set to the
overall timeout, so there will only ever be one attempt if this happens.
Using the channel_timeout instead will ensure that multiple connection
attempts are made even when the connection is wedged.
Fixes bug 1236524
Change-Id: Ie8dff41780bbf0 04cff5c880db202 a8ae23a85c1 ce0c34e338edf49 8258dfd721)
(cherry picked from commit b20cf3a30d42ed2