Cooldown period can be activated without scaling activity
Bug #1555748 reported by
Omar Soriano
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Rabi Mishra |
Bug Description
The cooldown behavior has changed after this commit:
https:/
Previously, if there was no change in the size of an autoscaling group, the cooldown period would not be activated. This seems to be the desired behavior, since we don't want a cooldown period when, say, a cpu_util low alarm kicks in and the minimum autoscaling size has already been reached.
Changed in heat: | |
importance: | Undecided → High |
milestone: | none → mitaka-rc1 |
Changed in heat: | |
importance: | High → Medium |
Changed in heat: | |
milestone: | mitaka-rc1 → mitaka-rc2 |
Changed in heat: | |
milestone: | mitaka-rc2 → newton-1 |
tags: | added: mitaka-backport-potential |
Changed in heat: | |
milestone: | newton-1 → mitaka-rc2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/291347
Review: https:/