test_server_rescue sets up two volumes, one for attach and one for detach - my guess is there is some parallel setup going on that is maybe making the volumes step on each other in cinder and that's slowing the test setup down to the point where it can sometimes fail.
So I think it might be valid to keep this as a tempest test failure. Maybe the volumes should be uniquely named in the tempest setup when it runs this?
I also see this show up twice in the last 7 days:
message:"Volume test_detach failed to reach available status within the required time" AND filename: "console. html"
http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwiVm9sdW1lIHRl c3RfZGV0YWNoIGZ haWxlZCB0byByZW FjaCBhdmFpbGFib GUgc3RhdHVzIHdp dGhpbiB0aGUgcmV xdWlyZWQgdGltZV wiIEFORCBmaWxlb mFtZTpcImNvbnNv bGUuaHRtbFwiIiw iZmllbGRzIjpbXS wib2Zmc2V0IjowL CJ0aW1lZnJhbWUi OiI2MDQ4MDAiLCJ ncmFwaG1vZGUiOi Jjb3VudCIsInRpb WUiOnsidXNlcl9p bnRlcnZhbCI6MH0 sInN0YW1wIjoxMz kwODQ2MjEwNjM1f Q==
test_server_rescue sets up two volumes, one for attach and one for detach - my guess is there is some parallel setup going on that is maybe making the volumes step on each other in cinder and that's slowing the test setup down to the point where it can sometimes fail.
So I think it might be valid to keep this as a tempest test failure. Maybe the volumes should be uniquely named in the tempest setup when it runs this?