"Timed out waiting for thing ... to become in-use" causes tempest-dsvm-* failures
Bug #1273292 reported by
Russell Bryant
This bug report is a duplicate of:
Bug #1270608: n-cpu 'iSCSI device not found' log causes gate-tempest-dsvm-*-full to fail.
Edit
Remove
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
Critical
|
John Griffith | ||
Bug Description
This is a spin-off of bug 1254890. That bug was originally covering failures for both timing out waiting for an instance to become ACTIVE, as well as waiting for a volume to become in-use or available.
It seems valuable to split out the cases of waiting for volumes to become in-use or available into its own bug.
message:"Details: Timed out waiting for thing" AND message:"to become" AND (message:"in-use" OR message:
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| importance: | High → Critical |
| milestone: | none → icehouse-3 |
| description: | updated |
| tags: | added: testing volumes |
| description: | updated |
Revision history for this message
| John Griffith (john-griffith) wrote | #1 |
| no longer affects: | cinder |
| Changed in nova: | |
| assignee: | nobody → John Griffith (john-griffith) |
To post a comment you must log in.
I believe this is a duplicate of: https:/
Checking here in this instance of the failure: http://
You can see nova timed out after 15 seconds waiting for the iscsi mount to complete. Given the VERY heavy load caused by this test I think it fits with the theory that these ops are horribly slow under heavy load.
I'm marking this as a duplicate, it's the same root cause regardless of whether it ends up that waiting longer helps us or not.