stack_delete fails/times out when soft-delete is enabled in nova
Bug #1377290 reported by
Sam Whyte
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Rakesh H S | ||
Juno |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When reclaim_
During this hang, if a force-delete is issued against the VM that Heat is "deleting", then Heat will acknowledge the state change and try to delete the next VM. In this way, a stack can be properly deleted if force-deletes are issued in the background.
This was first encountered in openstack-
Changed in heat: | |
assignee: | nobody → Rakesh H S (rh-s) |
Changed in heat: | |
status: | Triaged → Confirmed |
tags: | added: juno-backport-potential |
Changed in heat: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-1 → 2015.1.0 |
tags: | removed: juno-backport-potential |
To post a comment you must log in.
what state does a nova server go to when it is soft-deleted?