update combination alarm should not cause dependency dead loop
Bug #1309182 reported by
ZhiQiang Fan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Aodh |
Won't Fix
|
Undecided
|
Unassigned | ||
Ceilometer |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
assume we have threhold alarm C, D
then we create combination alarm A with alarm_ids = C, D
and we create combination alarm B with alarm_ids = A
then we update alarm A with alarm_ids = B
then when evaluator alarm state, the two combination alarm is a dead loop
we should avoid such secnarios
this bug is related to the blueprint: https:/
Changed in ceilometer: | |
assignee: | nobody → ZhiQiang Fan (aji-zqfan) |
Changed in ceilometer: | |
importance: | Undecided → Medium |
Changed in ceilometer: | |
assignee: | ZhiQiang Fan (aji-zqfan) → nobody |
status: | In Progress → Triaged |
Changed in ceilometer: | |
status: | Triaged → Won't Fix |
importance: | Medium → Undecided |
Changed in aodh: | |
importance: | Undecided → Medium |
Changed in aodh: | |
status: | In Progress → Invalid |
status: | Invalid → Won't Fix |
assignee: | ZhiQiang Fan (aji-zqfan) → nobody |
importance: | Medium → Undecided |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/88431
Review: https:/