Attach volume sometimes incorrectly reports success
Bug #673756 reported by
Devin Carlen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Recently while I was refactoring the smoke tests, I found that attach volume is reporting success even when the operation fails. I was able to work around this in the smoke tests by waiting longer before attaching. My initial sense is that the volume is reporting its state as "available" some small amount of time (5-15 seconds?) before it is really available.
Here is a snippet from the volume smoke tests that show how I was forced to work around the issue:
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
importance: | High → Medium |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | nobody → Ilya Pekelny (i159) |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
Changed in nova: | |
assignee: | Ilya Pekelny (i159) → nobody |
To post a comment you must log in.
The volume driver's create_export method should block until the device is actually ready. There must be some way to check when vblade (assuming the you're using AoE) has actually gotten its act together and exported the device?