Replaced resources can be left UPDATE_IN_PROGRESS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Zane Bitter |
Bug Description
If a resource requests a replacement, either by raising UpdateReplace the handle_update() method or by returning True from needs_replace_
However, if something fails and the stack is not rolled back, either because a subsequent resource update/create fails or the enginer dies, this leaves the resource stuck in an IN_PROGRESS state (it may be in the main stack or the backup stack). And this state is not reset when a new heat-engine starts up because the stack containing it will be correctly marked as FAILED.
It would be better to move these resources to the UPDATE_COMPLETE state, with the resource_
Changed in heat: | |
importance: | Undecided → Medium |
Changed in heat: | |
milestone: | none → newton-1 |
Fix proposed to branch: master /review. openstack. org/296080
Review: https:/