Child stack updates are not rolled back immediately in convergence
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Zane Bitter |
Bug Description
Thanks to various bug fixes, the stack-cancel-update command now works under convergence. However, it does not recursively cancel nested stacks. The nested stacks will eventually be updated as part of the rollback of the parent stack, but in the meantime they will continue updating resources that they'll eventually just have to roll back, and we won't be able to start said rollback at least until the current update has completed or failed. It would be more optimal if we could recursively stop the traversals on nested stacks as soon as we receive the stack-cancel-update command, so that we wouldn't do any unnecessary/
We now do basically that in the legacy path: where most resources have a grace period of 4 minutes to complete or fail before we cancel them (note: in convergence the grace period effectively extends until the stack timeout), resources that provide a handle_
An option I discussed with Anant in http://
description: | updated |
Changed in heat: | |
assignee: | Anant Patil (ananta) → Zane Bitter (zaneb) |
tags: | added: newton-rc-potential |
Changed in heat: | |
milestone: | next → newton-rc2 |
Changed in heat: | |
importance: | Medium → High |
Fix proposed to branch: master /review. openstack. org/370123
Review: https:/