Heat does not check in advance whether the stack can be deleted
Bug #1744694 reported by
Anatolii Neliubin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
New
|
Wishlist
|
Unassigned | ||
Bug Description
Detailed bug description:
When an instance created using Heat is in the "locked" state, heat service starts deleting does not check whether it can delete the whole stack or not.
Steps to reproduce:
Create the simplest Heat stack with one instance
Lock an instance using "nova lock" command
Delete the stack
Expected results:
Heat should refuse delete any resources in the stack
Actual result:
Some of resources are deleted.
Description of the environment:
MOS 8
| Changed in mos: | |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
