Failed update attempts might not preserve in heat the actual status of a resource
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
New
|
Undecided
|
Unassigned |
Bug Description
After an initial (and legit) update failure, a further update attempt (supposed to pass) might instead fail due to what seems to be a misrepresentation of the resources status in heat.
Here is a sample workflow:
1. create a stack (neutron net), with a nested stack (neutron port)
2. try to update the stack with an invalid and different implementation of a resource which would trigger a deletion
2bis. deletion is supposed to fail because the nested stack (neutron port) will prevent in neutron the deletion of the parent (neutron net)
3. try to update the stack again with a valid implementation of the same resource
3bis. update will continue to fail as heat will try to re-create the parent stack (neutron network) which hasn't ever been deleted
summary: |
- Failed update attempts might fail to preserve the heat representation of - a resource status + Failed update attempts might fail to preserve in heat the actual status + of a resource |
summary: |
- Failed update attempts might fail to preserve in heat the actual status - of a resource + Failed update attempts might not preserve in heat the actual status of a + resource |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
The attachment contains the templates and environments to be used to reproduce the issue as follows:
heat stack-create -e registry.yaml --template-file test.yaml test nooped. yaml --template-file test.yaml test
heat stack-update -e registry-
heat stack-update -e registry.yaml --template-file test.yaml test