Combination alarm doesn't change sate when one of alarms is in 'insufficient data' state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Low
|
ZhiQiang Fan |
Bug Description
Ceilometer 2014.2 Juno release.
When one of the alarms within combination one changes state to 'alarm' state and 2nd alarm is in 'insufficient data' state, then
combination alarm doesn't change state to 'alarm'.
Operator used with combination alarm 'OR'.
# ceilometer alarm-history 41517047-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-history 2792d7e9-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-history 1c260480-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-list
+------
| Alarm ID | Name | State | Enabled | Continuous | Alarm condition | Time constraints |
+------
| 1c260480-
| 2792d7e9-
| 41517047-
+------
[Triggering transition to 'alarm' state]
# ceilometer sample-create --meter-name 'alarm_meter_2' --resource-id 'alarm_resource_2' --meter-type 'cumulative' --meter-unit 'S' --sample-volume 8.0
+------
| Property | Value |
+------
| message_id | a97f5910-
| name | alarm_meter_2 |
| project_id | 85b6e8ab730b4dc
| resource_id | alarm_resource_2 |
| resource_metadata | {} |
| source | 85b6e8ab730b4dc
| timestamp | 2015-04-
| type | cumulative |
| unit | S |
| user_id | 9c1c7f2a7600433
| volume | 8.0 |
+------
# ceilometer alarm-history 1c260480-
+------
| Type | Timestamp | Detail |
+------
| state transition | 2015-04-
+------
# ceilometer alarm-history 2792d7e9-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-history 41517047-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-list
+------
| Alarm ID | Name | State | Enabled | Continuous | Alarm condition | Time constraints |
+------
| 1c260480-
| 2792d7e9-
| 41517047-
+------
[Waiting until alarm transitioned to 'inssufficient data' state]
# ceilometer alarm-list
+------
| Alarm ID | Name | State | Enabled | Continuous | Alarm condition | Time constraints |
+------
| 1c260480-
| 2792d7e9-
| 41517047-
+------
# ceilometer alarm-history 41517047-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-history 2792d7e9-
+------
| Type | Timestamp | Detail |
+------
+------
# ceilometer alarm-history 1c260480-
+------
| Type | Timestamp | Detail |
+------
| state transition | 2015-04-
| state transition | 2015-04-
+------
It would be great if 'alarm' state is considered as higher priority than 'insufficient data' state, at least for the 'OR' operator within combination alarm.
Or I'm missing something?
Thanks,
Yurii
Changed in ceilometer: | |
importance: | Undecided → Low |
Changed in ceilometer: | |
milestone: | none → liberty-1 |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | liberty-1 → 5.0.0 |
Fix proposed to branch: master /review. openstack. org/172515
Review: https:/