custom constraints can break stack-list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Thomas Spatzier | ||
Icehouse |
Fix Released
|
High
|
Thomas Spatzier |
Bug Description
If a custom constraint validates at stack-create time, then for some reason later fails to validate, you can no longer list any stacks:
$heat stack-create a123 -f shtmp.yaml -P "key_name=
$ heat stack-list
+------
| id | stack_name | stack_status | creation_time |
+------
| 91e79d75-
+------
$ nova keypair-delete stack_key
$ heat stack-list
ERROR: "stack_key" does not validate nova.keypair
Changed in heat: | |
status: | New → Confirmed |
assignee: | nobody → Steven Hardy (shardy) |
importance: | Undecided → High |
milestone: | none → juno-1 |
Changed in heat: | |
assignee: | Steven Hardy (shardy) → Thomas Spatzier (thomas-spatzier) |
status: | Confirmed → In Progress |
tags: | added: icehouse-backport-potential |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-1 → 2014.2 |
Actually you can't do anything with the stack which fails validation, including delete it