Bug 1036673

Summary:	Alert with avail_goes_not_up does not fire mutliple times when availability changes from DOWN to UNKNOWN
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	Monitoring - Alerts	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	theute
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-02 14:25:56 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-12-02 13:13:10 UTC

Description of problem:

This may be my wrong understanding of contition type AVAIL_GOES_NOT_UP. But I expect such alert to be fired anytime when availability of resource changes to state other than UP.


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

How reproducible: always


Steps to Reproduce:
1. have resource with availability UP
2. create alert definition for a resource with condition AVAIL_GOES_NOT_UP
3. set availability for resource as DOWN, wait 1 min
3. set availability for resource as UNKNOWN, wait 1 min

Actual results:

only 1 alert gets fired

Expected results:

2 alerts should be fired, because availability was changed twice to value other than UP

Comment 1 Libor Zoubek 2013-12-02 14:25:56 UTC

works as expected. 

jshaughn> The resource will need to go back UP and then go DOWN again to generate a second alert