Bug 571881

Summary: Modifying conditions on Alert Definition derived from Alert Template results in failure and stack trace in log
Product: [Other] RHQ Project Reporter: Steve Salevan <ssalevan>
Component: AlertsAssignee: Heiko W. Rupp <hrupp>
Status: CLOSED CURRENTRELEASE QA Contact: Bryan Kearney <bkearney>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: ckannan, smohan
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-12 16:58:39 UTC Type: ---
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:    
Bug Blocks: 565635    
Attachments:
Description Flags
resulting stacktrace none

Description Steve Salevan 2010-03-09 19:15:23 UTC
Description of problem:
If a user creates an Alert Template which applies to at least one of the resources within their RHQ environment and attempts to edit the conditions of the resulting Alert Definition upon one of these resources, the edit will fail, producing a red error box and a stack trace similar to that attached.

Version-Release number of selected component (if applicable):
RHQ, master branch, 4/9 git pull

How reproducible:
Always

Steps to Reproduce:
1. Create an Alert Template which applies to at least one of your resources
2. Edit the resulting Alert Definition on one of these corresponding resources
3. Add a new condition to this Alert Definition
  
Actual results:
Red error box and stacktrace

Expected results:
Edit completes successfully

Additional info:

Comment 1 Steve Salevan 2010-03-09 19:16:54 UTC
Created attachment 398893 [details]
resulting stacktrace

Comment 2 Heiko W. Rupp 2010-04-22 08:20:51 UTC
This is no longer an issue, as this part of the UI got rolled back to the old Struts UI.

Comment 3 gneelaka@redhat.com 2010-04-29 13:50:07 UTC
tested on JON#120 Revision 10615

Steps:

1)Go to Administration->System Configuration->templates.
2)select a platform  edit Alert templates.
3)Click on new template.
4)Enter the name,Description,condition and set it ok.
5)Now go to Resource -> Alert.


Observation: the new template definition is present with the name ,Description,Date created,Active,Parent (view template),read only (false) columns.

Go to the newly created template go to the alert properties click edit in the condition set section the alert properties get updated with the new condition. 
Also there  is no error displayed.



this is working fine now.

Comment 7 Corey Welton 2010-08-12 16:58:39 UTC
Mass-closure of verified bugs against JON.