+++ This bug was initially created as a clone of Bug #1357880 +++ Description of problem: ----------------------- Clone of upstream bug. A composite alarm continues to send notifications/log info about alarm transition even repeat_actions is set to False. Interesting that records in aodh/evaluator.log matches records from 'alarm history' output. 2016-05-11 10:15:08.143 93875 INFO aodh.notifier.rest [-] Notifying alarm Composite-Alarm 566bcde7-1757-4397-9585-c6efa3c7185b with severity critical from insufficient data to alarm with action SplitResult(scheme=u'http', netloc=u'127.0.0.1:15001', path=u'', query='', fragment='') because Composite rule alarm with composition form: (rule1 and rule2) transition to alarm, due to rules: rule1, rule2 outside their threshold.. request-id: req-e86b0f92-a267-4ed3-8289-724178d59547 2016-05-11 10:16:08.138 93875 INFO aodh.notifier.rest [-] Notifying alarm Composite-Alarm 566bcde7-1757-4397-9585-c6efa3c7185b with severity critical from alarm to alarm with action SplitResult(scheme=u'http', netloc=u'127.0.0.1:15001', path=u'', query='', fragment='') because Composite rule alarm with composition form: (rule1 and rule2) remaining as alarm, due to rules: rule1, rule2 outside their threshold.. request-id: req-57e6eb4a-3127-43f3-bcc2-4926539171e4 Version-Release number of selected component (if applicable): ------------------------------------------------------------- openstack-aodh-notifier-2.0.1-3.el7ost.noarch python-aodh-2.0.1-3.el7ost.noarch openstack-aodh-api-2.0.1-3.el7ost.noarch openstack-aodh-evaluator-2.0.1-3.el7ost.noarch python-aodh-tests-2.0.1-3.el7ost.noarch openstack-aodh-listener-2.0.1-3.el7ost.noarch openstack-aodh-common-2.0.1-3.el7ost.noarch
Waiting for next upstream liberty release to rebase the pkg
2.0.5 will be released upstream soon, with the fix https://review.openstack.org/#/c/368068/
I haven't updated the good BZ
For OSP8, we are waiting for 1.1.3 (and not 2.0.5).
Patches noted are present in rebase to 1.1.3
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-2016-2712.html