Bug 1040832

Summary: Group alert definition is not disabled when the alert is fired even though the 'Disable When Fired' is set
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Resource GroupingAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: ahovsepy, fbrychta, jshaughn
Target Milestone: ---   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-08 07:57:34 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 Filip Brychta 2013-12-12 08:28:55 UTC
Description of problem:
$Summary

Version-Release number of selected component (if applicable):
Version :	
3.2.0.GA
Build Number :	
7b00246:6d13523

How reproducible:
Always

Steps to Reproduce:
1. create compatible group containing 2 platforms
2. create following alert definition on this group:
   Alert _Name_: 'testAlert'
   Condition:       
        *   _Condition Type_: _Operation Execution_
        *   _Value_: _Manual Autodiscovery_
        *   _Status_: _Success_
   Recovery:        
        *   _Disable When Fired_ : _Yes_
3. invoke operation _Manual Autodiscovery_ on this group


Actual results:
Alerts are correctly fired, but group 'testAlert' alert definition is still enabled.
Alert definitions visible on both children are correctly disabled.

Expected results:
Group 'testAlert' alert definition is disabled as well

Comment 2 Jay Shaughnessy 2014-09-05 19:06:54 UTC
I agree this is can be confusing, but this is the expected behavior.  A Group alert definition behaves basically like an alert definition template.  The actual alert definition is not actually processed at the group level but rather just pushed down the definitions to all of it's group member resources.  Only the resource-level definitions actually get processed/fired/disabled/recovered.

We don't really have any "true" alerting at the group level, although this is something we'd like to see in the next gen of alerting.

Filip, does this resolve the issue? If so please close, otherwise, just respond with your follow-up. Thanks.