openstack stack update --dry-run wrongly requires an existing stack
Bug #1602301 reported by
Honza Pokorny
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-heatclient |
Fix Released
|
Undecided
|
Rabi Mishra | ||
Bug Description
Running "heat stack-preview" doesn't require an existing stack to run. It's useful when gathering information about a set of heat templates on the fly. "heat stack-preview" is giving me a deprecation warning and suggests that I use "openstack stack update --dry-run". This new openstack command doesn't work for the above scenario because it requires an existing stack.
Revision history for this message
| Rabi Mishra (rabi) wrote | #1 |
| Changed in python-heatclient: | |
| assignee: | nobody → Rabi Mishra (rabi) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-heatclient (master) | #2 |
| Changed in python-heatclient: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-heatclient (master) | #3 |
| Changed in python-heatclient: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote Fix included in openstack/python-heatclient 1.3.0 | #4 |
To post a comment you must log in.
I think the deprecation message is wrong.
you can use 'openstack stack create --dry-run' instead.