Bug 567769 - Clicking "View Template" link on individual resource's Alert Definitions page results in stack trace
Summary: Clicking "View Template" link on individual resource's Alert Definitions page...
Keywords:
Status: CLOSED DUPLICATE of bug 566896
Alias: None
Product: RHQ Project
Classification: Other
Component: Alerts
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Heiko W. Rupp
QA Contact: Steve Salevan
URL:
Whiteboard:
Depends On:
Blocks: rhq_chainsaw
TreeView+ depends on / blocked
 
Reported: 2010-02-23 21:01 UTC by Steve Salevan
Modified: 2010-02-24 13:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-24 13:40:47 UTC
Embargoed:

Attachments (Terms of Use)
Stack trace (4.18 KB, text/plain)
2010-02-23 21:01 UTC, Steve Salevan 		no flags Details
View All

Description Steve Salevan 2010-02-23 21:01:27 UTC 
Created attachment 395822 [details]
Stack trace

Description of problem:
If a user creates an Alert Template which is applied to all of their available resources, then visits (Resource Page->Alert tab->Definitions) and clicks on the "View Template" link for the applied Alert Template, a stack trace will result.

Version-Release number of selected component (if applicable):
RHQ-alertPlugin branch, 2/18 git pull

How reproducible:
Always

Steps to Reproduce:
1. Create an Alert Template for a particular type of resource
2. Visit the resource page for a corresponding resource
3. Visit the Alert tab and Definitions subtab
4. Click the "View Template" link related to the Alert Template you just created
  
Actual results:
Stack trace (attached)

Expected results:
No stack trace

Additional info:
Comment 1 Bryan Kearney 2010-02-24 12:55:20 UTC 
Is this a dupe?
Comment 2 Heiko W. Rupp 2010-02-24 13:15:58 UTC 
No, this is still active
Comment 3 Heiko W. Rupp 2010-02-24 13:40:47 UTC 
Ah yes, this is a dup of https://bugzilla.redhat.com/show_bug.cgi?id=566896

*** This bug has been marked as a duplicate of bug 566896 ***
Note You need to log in before you can comment on or make changes to this bug.