Below is the description about how "repeat_actions" would work,
# heat resource-type-show OS::Ceilometer::Alarm
... ...
"repeat_actions": {
"description": "False to trigger actions when the threshold is reached AND the alarm's state has changed. By default, actions are called each time the threshold is reached.",
"default": "true",
"required": false,
"update_allowed": true,
"type": "boolean",
"immutable": false
},
... ...
It states that the default value should be "true', even it isn't be explicitly set in the template.
But it seems the default value is false if not being set in the template. Actions are not called if alarm's state has NOT been changed.
Here are logs when "repeat_actions" was not set,
+---------------------------+--------------------------------------------------------------------------+
| Property | Value |
+---------------------------+--------------------------------------------------------------------------+
| alarm_actions | [u'http://172.16.100.88:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Add0d5 |
| | 8342c4d4a36925943f572038fe9%3Astacks%2Fs-01%2F9b794a80-3c45-45d4-a39d-a6 |
| | 49d7512fcd%2Fresources%2FMultiregionScalingPolicy?Timestamp=2014-09-29T0 |
| | 7%3A24%3A16Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=c688601f35b543d2a |
| | 632f90d916ddf5e&SignatureVersion=2&Signature=yrCPf4%2BDniStzEsNywpy%2Fzr |
| | 5l9CzGFfPTYTcI45FZdI%3D'] |
| alarm_id | b8f0a5ab-f2c3-4b2c-b5af-4cf5cad24da3 |
| comparison_operator | lt |
| description | ScalingAlarmDownOne |
| enabled | True |
| evaluation_periods | 1 |
| exclude_outliers | False |
| insufficient_data_actions | [] |
| meter_name | cpu_util |
| name | s-01-ScalingAlarmOne-tsxzpgfdhopo-CPUAlarmLow-czpvgujdtskr |
| ok_actions | [] |
| period | 60 |
| project_id | dd0d58342c4d4a36925943f572038fe9 |
| query | metadata.user_metadata.stack == 9b794a80-3c45-45d4-a39d-a649d7512fcd |
| repeat_actions | False |
| state | ok |
| statistic | avg |
| threshold | 20.0 |
| type | threshold |
| user_id | bd222bd40a374d8181a716b3127411e6 |
+---------------------------+--------------------------------------------------------------------------+
This should be caused by erroneous properties handling of ceilometer alarm resource.