Bug 552335

Summary:	Configured Alert Sender Plugins disappear from 'Add a sender' selector box on 'New Alert Sender stuff' page
Product:	[Other] RHQ Project	Reporter:	Steve Salevan <ssalevan>
Component:	Plugins	Assignee:	Justin Harris <jharris>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	bkearney, ckannan, jkeck, whayutin
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:44: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:	547833, 565617

Description Steve Salevan 2010-01-04 18:20:10 UTC

Description of problem:
If a user configures one of the Alert Sender Server-Side Plugins and attempts to add this Alert Sender to an Alert, the Alert Sender will disappear from the 'Add a sender' selector box on the 'New Alert Sender stuff' page after configuration.

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

How reproducible:
Always

Steps to Reproduce:
1. Configure an alert sender plugin (SNMP or IRC were the senders I configured)
2. Create an alert for a resource
3. Goto <page for your resource>->Alert tab-><the name of your new alert>->'New Alert Sender stuff'
4. Attempt to select configured alert sender plugin from the 'Add a sender' selector box
  
Actual results:
Configured plugin not present in selector box

Expected results:
Configured plugin present in selector box

Additional info:

Comment 1 Justin Harris 2010-01-25 15:59:36 UTC

Its been a while since this was reported, but it works for me in the current version.

Comment 2 wes hayutin 2010-02-17 13:27:18 UTC

mass move to rhq_chainsaw tracker bug

Comment 3 wes hayutin 2010-02-18 14:49:50 UTC

This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10.

Comment 4 Bryan Kearney 2010-02-18 20:45:01 UTC

Fix for this is in master as of 3.0.0-B3.

Comment 5 wes hayutin 2010-02-22 21:22:17 UTC

verified this is no longer an issue in.
commit 3602414a6baff7fb52d637d2006574610212b46f

Comment 6 wes hayutin 2010-03-10 14:19:40 UTC

moving verified bugs to rhq_sprint06, and removing from rhq_chainsaw

Comment 10 Corey Welton 2010-08-12 16:44:39 UTC

Mass-closure of verified bugs against JON.