Can not delete stack if volume go to error_deleting state
Bug #1387978 reported by
Sergey Kraynev
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Low
|
Unassigned |
Bug Description
Some times volumes may go to state error_deleting.
There are some ways to delete them: via force delete or manually from db.
On Heat side it leads to stack which can not be deleted, because it's constantly meet error that:
Error Resource deletion with status error_deleting.
Should we handle it in the Heat?
Changed in heat: | |
assignee: | nobody → Song Li (lisong-cruise) |
Changed in heat: | |
assignee: | Song Li (lisong-cruise) → nobody |
Changed in heat: | |
status: | New → Triaged |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
I don't see how we can handle it in heat, if it's a persistent failure, the best we can do is ignore it.
A possible option would be a --ignore-error option or similar which forces traversal of the whole stack even when we encounter an error (which is not sure to succeed because there may be a dependency on the thing which can't be deleted).
IMO this is a cinder bug, so it's probably best to debug the root cause of the delete volume error.