Constant ALARM state means only one actions event is ever emitted
Bug #1193970 reported by
Steve Baker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steve Baker |
Bug Description
If a watch rule goes into an ALARM state and stays in the ALARM state, only one actions event is ever emitted.
In the example where bringing up one new server isn't sufficient to reduce the load below the alarm threshold, no new servers are ever created.
Changed in heat: | |
assignee: | nobody → Steve Baker (steve-stevebaker) |
milestone: | none → havana-2 |
importance: | Undecided → High |
status: | New → In Progress |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/34158
Review: https:/