Backup stacks should be hard-deleted
Bug #1332300 reported by
Zane Bitter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Unassigned |
Bug Description
During a stack update, we create a "backup" stack in which we temporarily store resources we are expecting to delete later while their replacements are created. Due to the fact that stacks are only soft-deleted, the backup stack, its template, and any associated resources are not removed from the DB when the update completes successfully. (They will be removed when the operator does a periodic clean-out of deleted stacks.)
This is both a waste of DB space and could cause potentially cause problems (in _theory_ it's OK...) on a future update due to the out-of-date template & resources. We should probably do a hard delete of the backup stack on conclusion of a successful stack update.
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in heat: | |
assignee: | nobody → Anant Patil (anant-techie) |
Changed in heat: | |
status: | Triaged → In Progress |
Changed in heat: | |
milestone: | none → juno-3 |
Changed in heat: | |
milestone: | juno-3 → juno-rc1 |
Changed in heat: | |
milestone: | juno-rc1 → next |
Changed in heat: | |
milestone: | next → none |
Changed in heat: | |
assignee: | Anant Patil (ananta) → Ishant Tyagi (ishant-tyagi) |
Changed in heat: | |
assignee: | Ishant Tyagi (ishant-tyagi) → Rakesh H S (rh-s) |
Changed in heat: | |
assignee: | Rakesh H S (rh-s) → nobody |
Changed in heat: | |
status: | In Progress → Triaged |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
Is there a particular test case which failed for you? I did a simple test where I had only VMs as resources and when I update the stack, the old resources (VMs) are deleted.