Comment 4 for bug 1254772

Revision history for this message
Matt Riedemann (mriedem) wrote :

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/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVm9sdW1lIHRlc3RfZGV0YWNoIGZhaWxlZCB0byByZWFjaCBhdmFpbGFibGUgc3RhdHVzIHdpdGhpbiB0aGUgcmVxdWlyZWQgdGltZVwiIEFORCBmaWxlbmFtZTpcImNvbnNvbGUuaHRtbFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzkwODQ2MjEwNjM1fQ==

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?