tempest volume scenarios periodically fail /w SSHTimeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Undecided
|
Unassigned | ||
grenade |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Not sure this is a duplicate, but I've noticed failing tempest volume scenarios as part of grenade tests, ie
Traceback (most recent call last):
File "tempest/test.py", line 128, in wrapper
return f(self, *func_args, **func_kwargs)
File "tempest/
keypair)
File "tempest/
private_
File "tempest/
linux_
File "tempest/
self.
File "tempest/
connection = self._get_
File "tempest/
password=
SSHTimeout: Connection to the 172.24.4.2 via SSH timed out.
User: cirros, Password: None
Checking logstash these seem to be happening frequently during grenade jobs, failing both test_snapshot_
summary: |
- grenade volume scenarios periodically fail /w SSHTimeout + tempest volume scenarios periodically fail /w SSHTimeout |
tags: | added: testing |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → Won't Fix |
Changed in grenade: | |
status: | New → Invalid |
Yeah this is a known thing, the ssh timeout failure is generic so it's hard to classify in elastic-recheck:
http:// logs.openstack. org/71/ 179971/ 2/gate/ gate-grenade- dsvm/eb2fb74/ logs/grenade. sh.txt. gz#_2015- 05-20_07_ 26_25_655
I think we'll need a change to tempest to log a specific error for the test in this case so we can track this bug.