Bug 1035890

Summary:	Alert with trait value change condition does not get fired when data is pushed through REST api
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	Monitoring - Alerts, REST	Assignee:	Thomas Heute <theute>
Status:	CLOSED EOL	QA Contact:	Sunil Kondkar <skondkar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	fbrychta, loleary, myarboro, theute
Target Milestone:	---	Keywords:	NeedsTestCase
Target Release:	JON 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-10 14:48:08 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:

Description Libor Zoubek 2013-11-28 18:14:12 UTC

Description of problem:


Version-Release number of selected component (if applicable):
JON 3.2.ER7

How reproducible: always


Steps to Reproduce:
1. create syntetic platform via rest
2. choose a trait (ie. Trait.osname)
3. create alert def with traitValueChange condition type
4. push trait using rest api so condition for your alert is met

Actual results:

alert does not get fired

Expected results:

alert gets fired

Additional info:

I'll provide automated test once I push it to github

Comment 1 Libor Zoubek 2013-12-12 13:42:01 UTC

You can run test to detect/verify this bug:

go through https://github.com/RedHatQE/jon-tests/blob/master/alerts/README.md

git clone https://github.com/RedHatQE/jon-tests.git
cd jon-tests
nosetests -a "single,trait"

Comment 4 Lukas Krejci 2014-08-28 12:11:43 UTC

*** Bug 1041079 has been marked as a duplicate of this bug. ***

Comment 5 Lukas Krejci 2014-08-28 12:12:00 UTC

*** Bug 1058658 has been marked as a duplicate of this bug. ***

Comment 6 Lukas Krejci 2014-08-28 12:12:44 UTC

Moving this to post-GA.

While the impl for this is mostly ready (https://github.com/rhq-project/rhq/pull/51), there are still some TODOs mentioned but more importantly, the fix introduces a whole new type of resources (synthetic) and quite big changes across the codebase to correctly support these.

I find this too risky to include in JON 3.3 without prior bake time in RHQ.

Comment 7 Larry O'Leary 2015-01-12 17:32:40 UTC

As per Libor, the fix for this will require schema changes and therefore can not go into an update. Setting target for consideration in a future minor/major release.

Comment 10 Filip Brychta 2019-06-10 14:48:08 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.