composite alarm - transition to insufficient data, due to rules: state evaluated to unknown
Bug #1645344 reported by
Mehdi Abaakouk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Aodh |
Fix Released
|
Undecided
|
Mehdi Abaakouk |
Bug Description
AODH failed properly evaluate composite alarm and transitioned it to unknown state:
aodh.evaluator [-] alarm ecdeee1d-
More detail downstream: https:/
Changed in aodh: | |
assignee: | nobody → Mehdi Abaakouk (sileht) |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/403739 /git.openstack. org/cgit/ openstack/ aodh/commit/ ?id=0ac9fcaf625 998da147bdd1aa3 e290b40b2d0282
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0ac9fcaf625998d a147bdd1aa3e290 b40b2d0282
Author: Mehdi Abaakouk <email address hidden>
Date: Mon Nov 28 15:40:59 2016 +0100
composite: fix evaluation of trending state alarms
When threshold evaluator returns a trending state instead of a state,
the composite evaluator ignores it and passes the alarm to insufficient
data instead of using it.
This change fixes that.
Closes-bug: #1645344
Change-Id: I4703936e0377a4 66e09c97b548519 1b17442b57d