Bug 1091965 - Unable to create second alert definition in RHQ GUI, throws "Failed to get notification configuration preview"
Summary: Unable to create second alert definition in RHQ GUI, throws "Failed to get no...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1382649
TreeView+ depends on / blocked
 
Reported: 2014-04-28 12:03 UTC by Jeeva Kandasamy
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
RHQ Alert Definitions failure (66.88 KB, application/gzip)
2014-04-28 12:03 UTC, Jeeva Kandasamy
no flags Details

Description Jeeva Kandasamy 2014-04-28 12:03:15 UTC
Created attachment 890450 [details]
RHQ Alert Definitions failure

Description of problem:
If you create second alert definition via GUI, throws "Failed to get notification configuration preview".

Version-Release number of selected component (if applicable):
Version : 4.11.0-SNAPSHOT
Build Number : 3df85a2
GWT Version : 2.5.0
SmartGWT Version : 3.0

Firefox ESR 17

How reproducible:
always

Steps to Reproduce:
1. Navigate to "Inventory-->Servers-->RHQ Agent-->Alert-->Definition"
2. Click on "New"
3. In "General Properties", Enter Alert name
4. Navigate to Conditions, Add a condition like, "Condition Type: Measurement Absolute Value Threshold, Metric: Agent server Clock Different", Fill some values for other boxes
5. Navigate to "Notifications", Click Add, "Notification Sender: System User", select assigned user as "rhqadmin", Click OK
6. Click on "Save"
7. Click on "Back to List"
8. Repeat from Step #2 again



Unable to create more than on Alert Definition, There is an error while selecting "Notification Sender" from second alert definition.

Additional info: Screen shot and log files are attached.


Note You need to log in before you can comment on or make changes to this bug.