Autoscaling nested stack update incorrectly implemented
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld |
Bug Description
In a couple of places we've got this happening:
updater = self.update_
updater.
self.
This means all update operations involving InstanceGroup and AutoScalingGroup resources will be serialized, since we're not following the correct pattern where we start the update in handle_update and poll for completion in check_create_
This will become a more problematic issue when we move to decoupled nested stacks, since it means the parent stack will block on the nested stack update, when it could be doing something else and just periodically polling the nested stack state in check_update_
Changed in heat: | |
assignee: | nobody → Steven Hardy (shardy) |
Changed in heat: | |
assignee: | Steven Hardy (shardy) → Angus Salkeld (asalkeld) |
milestone: | next → kilo-3 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-3 → 2015.1.0 |
Additional notes:
- stack-update initiated updates of InstanceGroup resource counts will block in the parent stack
- check_update_ complete is only called once, so we don't actually wait for the update to complete when doing rolling updates etc.