diablo: race condition between server delete and image-create
Bug #944116 reported by
David Kranz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
In diablo, but not in essex, if you 'nova delete' a vm and then immediately 'nova image-create' on the deleted server, the image-create command will not fail and an image will be 'created' that is wedged in the SAVING state.
Revision history for this message
| Thierry Carrez (ttx) wrote | #1 |
| Changed in nova: | |
| status: | New → Invalid |
Revision history for this message
| David Kranz (david-kranz) wrote | #2 |
| no longer affects: | nova/diablo |
To post a comment you must log in.
What do you mean by "diablo" here ? The original 2011.3 release ? The subsequent 2011.3.1 release ? Or the current state of stable/diablo branch ?