heat stack-delete does not report immediately error for an unexist stack
Bug #1592700 reported by
Guoping Jia
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-heatclient |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Starting from recent heatclient, the heat stack-delete explicitly prompts for a confirmation before it starts deletion. This is true even for an unexisting heat stack.
$ heat --version
1.1.1
$ heat stack-delete hqaxxx
Are you sure you want to delete this stack(s) [y/N]? y
ERROR: The Stack (hqaxxx) could not be found.
Unable to delete 1 of the 1 stacks.
The heat stack-delete then fails when you choose yes.
I am not sure if it's a feature or a bug ? It looks pretty confusing.
Revision history for this message
| Thomas Herve (therve) wrote | #1 |
| affects: | heat → python-heatclient |
| Changed in python-heatclient: | |
| status: | New → Won't Fix |
To post a comment you must log in.
I don't think it's really damaging.