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 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to aodh (master) | #1 |
| Changed in aodh: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to aodh (stable/newton) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to aodh (stable/newton) | #3 |
| tags: | added: in-stable-newton |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/aodh 4.0.0 | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/aodh 3.0.2 | #5 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0ac9fcaf625998d
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