AlarmCombination resource repeat_actions property has no effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Eoghan Glynn | ||
Juno |
Fix Released
|
Undecided
|
Eoghan Glynn |
Bug Description
In order to drive Heat autoscaling, the repeat_actions attribute of a Ceilometer alarm must be set to true (as the autoscaling logic requires a continuing stream of notifications that alarm remains in the target state).
In the case of a combination alarm, the value of the repeat_actions property has no effect on the alarm creation, so this attribute defaults to false on the Ceilometer side.
This occurs because the Heat AlarmCombination resource incorrectly places the repeat_actions value within the combination rule, instead of at the top-level of the alarm representation:
{"alarm_actions": [<URL>], "type": "combination", "combination_rule": {"operator": "and", "alarm_ids": ["ALARM1_ID", "ALARM2_ID"], "repeat_actions": true}, "name": "Combination Alarm"}
instead of:
{"alarm_actions": [<URL>], "type": "combination", "combination_rule": {"operator": "and", "alarm_ids": ["ALARM1_ID", "ALARM2_ID"]}, "repeat_actions": true, "name": "Combination Alarm"}
Changed in heat: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
status: | New → In Progress |
tags: | added: icehouse-backport-potential juno-backport-potential |
Changed in heat: | |
importance: | Undecided → High |
milestone: | none → kilo-1 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-1 → 2015.1.0 |
tags: |
added: in-stable-juno removed: juno-backport-potential |
Fix proposed to branch: master /review. openstack. org/135576
Review: https:/