make the ceilometer alarm repeat_action true by default
Bug #1242168 reported by
Angus Salkeld
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld |
Bug Description
The policy actions assume repeat_
For the situation when cpu is high even when a new server is added.
Here we would expect yet-another server to be added but what currently
happens is the alarm will be stuck in the alarm state, but with no
further actions.
We need a default that it sane.
Refer also to bug #1223347
Changed in heat: | |
assignee: | nobody → Angus Salkeld (asalkeld) |
importance: | Undecided → Medium |
status: | New → Triaged |
milestone: | none → icehouse-1 |
Changed in heat: | |
status: | Triaged → In Progress |
Changed in heat: | |
status: | Fix Committed → Fix Released |
tags: | added: havana-backport-potential |
tags: | added: havana-backport-potential |
Changed in heat: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/52541 github. com/openstack/ heat/commit/ 4dc987eff3a6963 706253a7007c794 ca75326d2e
Committed: http://
Submitter: Jenkins
Branch: master
commit 4dc987eff3a6963 706253a7007c794 ca75326d2e
Author: Angus Salkeld <email address hidden>
Date: Wed Oct 23 07:33:45 2013 -1000
Repeat Ceilometer alarm actions by default
The policy actions assume repeat_ actions= true.
For the situation when cpu is high even when a new server is added.
Here we would expect yet-another server to be added but what currently
happens is the alarm will be stuck in the alarm state, but with no
further actions.
We need a default that it sane.
Closes-bug: #1242168 01ebd0d7431d3fa c559161e947
Related-bug: #1223347
Change-Id: I4c6a084076a0cc