Bug 1357880

Summary:	Alarm ignores repeat_actions field
Product:	Red Hat OpenStack	Reporter:	Yurii Prokulevych <yprokule>
Component:	openstack-aodh	Assignee:	Mehdi ABAAKOUK <mabaakou>
Status:	CLOSED ERRATA	QA Contact:	Yurii Prokulevych <yprokule>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	apevec, fbaudin, jschluet, lhh, mburns, mlopes, pkilambi
Target Milestone:	ga	Keywords:	Triaged
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-aodh-2.0.3-2.el7ost	Doc Type:	Bug Fix
Doc Text:	Prior to this update, composite alarms continued to send notifications on each refresh. This resulted in unnecessary notifications appearing in the log files. This update addresses this by no longer sending notifications on each alarm refresh.	Story Points:	---
Clone Of:
Clones:	1357918 (view as bug list)		Environment:
Last Closed:	2016-08-15 07:19:51 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:
Bug Depends On:	1360399
Bug Blocks:	1357918

Description Yurii Prokulevych 2016-07-19 13:02:05 UTC

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

Comment 3 Yurii Prokulevych 2016-07-29 15:34:05 UTC

Alarm doesn't log on each evaluation cycle.

aodh --debug alarm create \
--type composite \
--name 'Composite-GnResource-Threshold' \
--description 'Gnocchi-Resource-Threshold and Threshold' \
--severity critical \
--enabled True \
--alarm-action 'log://' \
--ok-action 'log://' \
--insufficient-data-action 'log://' \
--evaluation-periods 3 \
--composite-rule '{ "and": [ { "meter_name": "custom.meter.1", "evaluation_periods": 3, "period": 60, "statistic": "avg", "threshold": 4.0, "query": [{"field": "resource_id", "type": "", "value": "Overcloud-Resource-1", "op": "eq"}], "type": "threshold", "comparison_operator": "ge" }, { "aggregation_method":"mean", "comparison_operator":"ge", "evaluation_periods": 3, "granularity": 60, "metric": "radosgw.objects", "resource_id": "my-ceph-1", "resource_type": "ceph_account", "threshold": 4, "type": "gnocchi_resources_threshold" } ]}'

Packages:
---------
openstack-aodh-notifier-2.0.3-2.el7ost.noarch
python-aodh-2.0.3-2.el7ost.noarch
openstack-aodh-evaluator-2.0.3-2.el7ost.noarch
openstack-aodh-common-2.0.3-2.el7ost.noarch
openstack-aodh-listener-2.0.3-2.el7ost.noarch
openstack-aodh-api-2.0.3-2.el7ost.noarch

Comment 5 errata-xmlrpc 2016-08-15 07:19:51 UTC

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/RHEA-2016-1597.html