Bug 1398339
Summary: | AODH: composite alarm - transition to insufficient data, due to rules: state evaluated to unknown | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yurii Prokulevych <yprokule> |
Component: | openstack-aodh | Assignee: | Mehdi ABAAKOUK <mabaakou> |
Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 10.0 (Newton) | CC: | apevec, fbaudin, jdanjou, jschluet, lhh, mlopes, nlevinki, pkilambi |
Target Milestone: | z2 | Keywords: | Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-aodh-3.0.1-6.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Prior to this update, the aodh composite alarm would not compute the final alarm state correctly. This occurred when one alarm only had a trending state and not a hard state. The trending state occurrs only when the alarm monitors new data, which is usually just after an alarm is created, or when the resource that the alarm monitors is created.
Consequently, the aodh composite alarm would report the incorrect state at the beginning of the alarm life.
With this update, the aodh has been updated to openstack-aodh-3.0.1-6.el7ost.
As a result, the aodh composite alarm no longer reports the incorrect state.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-01 13:38:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yurii Prokulevych
2016-11-24 13:33:42 UTC
landed on upstream/stable/newton updating external tracker with that patch https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS10/job/qe-phase2-10_director-rhel-7.3-virthost-1cont_1comp_1ceph-ipv4-vxlan-ceph/76/ All regression tests passed with no errors and the right rpm is in the puddle. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0355.html |