Extra instance is created if evaluation period set short
Bug #1375156 reported by
Hang Liu
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Yanyan Hu | ||
Juno |
Fix Released
|
Medium
|
Zane Bitter | ||
Kilo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If evaluation period is set shorter than the instance starting time. And 'repeat_actions' is set to True.
Extra instances would be created, even the cooldown time has been set long enough.
Possible Reasons:
1) No guarding logic at alarm signals in ASG code.
2) If the 2nd instance starts up slow, a 2nd alarm may arrive before the 2nd instance is ready.
3) The very first 'cooldown' timestamp is not computed/set because the 2nd instance is not ready. So the 3rd instance (maybe the 4th, 5th, ... instances are quickly launched).
Changed in heat: | |
assignee: | nobody → Qiming Teng (tengqim) |
status: | New → Confirmed |
Changed in heat: | |
importance: | Undecided → Medium |
Changed in heat: | |
status: | In Progress → Fix Committed |
tags: | added: juno-backport-potential kilo-backport-potential |
Changed in heat: | |
milestone: | none → liberty-2 |
status: | Fix Committed → Fix Released |
tags: | removed: kilo-backport-potential |
Changed in heat: | |
milestone: | liberty-2 → 5.0.0 |
tags: | removed: juno-backport-potential |
To post a comment you must log in.
Should we add a para to indicate the status of ASG, for example, PROGRESS, COMPLETE. If the status of ASG resource is process autoscaling, then any signal will be ignored. Only if that the ASG status is COMPLETE and out of cool down time can scale.