Intermittent ssh tempest timeouts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Two tempest tests intermittently fail while running our CI. These tests also fail when using LVM as a backend so they are not related one particular driver.
test_volume_
test_minimum_
Scenario
A VM is rebooted and then the test tries to ssh back into the VM. The ssh fails with the specific error (timeout). It will retry for 4-6 times before failing to connect and failing the test case.
SSH errors that occur but do not cause test case failure
There is built in code that retries the ssh connection to give the VM time to boot up. The errors seen in the case are ([Errno 111] Connection refused) and (Authentication failed) and ([Errno 113] No route to host). If these errors are seen the ssh connection is eventually successful and the test case moves on.
The error strings in parens () above are what show up in this log line. When the error is (timed out) as below the test always fails.
12:33:13 2015-06-18 12:26:50,762 5533 WARNING [tempest_
Changed in tempest: | |
status: | New → Confirmed |
Adding an etherpad that contains some notes.
https:/ /etherpad. openstack. org/p/Tempest_ SSH_Timeouts