Bug 599538 - Resource operation alert does not find a resource
Summary: Resource operation alert does not find a resource
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Alerts
Version: 3.0.0
Hardware: All
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Joseph Marques
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks: jon24-alert-scripts
TreeView+ depends on / blocked
 
Reported: 2010-06-03 13:21 UTC by Lukas Krejci
Modified: 2010-08-12 16:59 UTC (History)
0 users

Fixed In Version: 2.4
Clone Of:
Environment:
Last Closed: 2010-08-12 16:59:25 UTC
Embargoed:


Attachments (Terms of Use)

Description Lukas Krejci 2010-06-03 13:21:24 UTC
Description of problem:

I have a JBossAS server with a custom script in $JBOSS_HOME/bin that gets correctly discovered by RHQ (the script is executable). 

I created an alert on Free Memory value change and set up an "Resource Operation" alert sender to find a relative resource starting the search from JBossAS Server, then filtering by type "Script" and name "test-script.sh" (which is the name of the script file as well as the RHQ resource that represents it). I also tried to put the resource's resource key instead of just the name.

Yet each time the alert fires the notification action fails with message "<no resource selected>".

How reproducible:
always

Actual results:
The script is never run.

Expected results:
The script should run.

Comment 1 Joseph Marques 2010-06-04 17:41:32 UTC
commit 0b1c4a0f06acedf07e695e4b7c30bcbc372b8bcf
Author: Joseph Marques <joseph>
Date:   Fri Jun 4 13:38:30 2010 -0400

BZ-599538: fix error handling for executing alert-trigger operation using RELATIVE search

Comment 2 Charles Crouch 2010-06-04 18:25:05 UTC
Lukas, can you retest this please.

Comment 3 Lukas Krejci 2010-06-07 12:47:22 UTC
seems to work in Beta1

Comment 4 Sudhir D 2010-06-10 14:25:04 UTC
I have verified this and it is working in Beta1. Marking this bug as verified.

Comment 5 Corey Welton 2010-08-12 16:59:25 UTC
Mass-closure of verified bugs against JON.


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