cinder volume deletions-in-progress lead to stack deletion errors
Bug #1362708 reported by
Joe D'Andrea
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Rakesh H S |
Bug Description
Scenario: A stack containing a significantly-sized OS::Cinder::Volume has been queued for deletion via stack-delete (not out-of-band).
Consider the case where this stack deletion was interrupted (e.g., an error). Meanwhile, the cinder volume still happens to be in a deleting state.
The stack-delete request is made once again, and a new error is thrown:
http://
I propose that Heat should gracefully ignore the volume and not throw an error, as it is already being deleted.
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in heat: | |
assignee: | nobody → Rakesh H S (rh-s) |
Changed in heat: | |
importance: | Medium → High |
Changed in heat: | |
status: | Confirmed → In Progress |
Changed in heat: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
I was able to reproduce this issue