Bug 547864

Summary:	Twitter only updated once upon multiple alert firings
Product:	[Other] RHQ Project	Reporter:	Steve Salevan <ssalevan>
Component:	Alerts	Assignee:	Heiko W. Rupp <hrupp>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.4.0.B01	CC:	ckannan, hrupp
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:51:35 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:	555091
Bug Blocks:	547833, 565617

Description Steve Salevan 2009-12-15 20:28:23 UTC

Description of problem:
If a user configures an alert to update Twitter upon firing (using the Twitter Alert Sender plugin), Twitter will only be updated upon its first firing and will not be thereafter.

Version-Release number of selected component (if applicable):
RHQ, master branch, 12/15/09 git pull

How reproducible:
Always

Steps to Reproduce:
1. Create an alert that fires repeatedly, ensure that the 'Disable alert until re-enabled manually or by recovery alert' flag is unset
2. Configure alert to update Twitter
  
Actual results:
Twitter only updated upon first alert firing

Expected results:
Twitter updates correspond with respective alert firing

Additional info:

Comment 1 Heiko W. Rupp 2009-12-17 10:14:02 UTC

Did you after the alert fired for the first time update the plugin (re-deploy it)?

Can you check if after the first firing the username and password are still filled in in the plugin preference?

Comment 2 Steve Salevan 2009-12-17 16:28:55 UTC

Alas, the username and password are still filled in after the first firing.

Comment 3 Heiko W. Rupp 2010-01-13 15:27:33 UTC

I can not reproduce this.

the microblog sender is now logging the status id to system log upon sending.

Comment 4 Heiko W. Rupp 2010-01-28 09:38:08 UTC

I think this is the same as BZ 555091 - Twitter is actively filtering duplicate tweets.
I've added the (unique) alert id to the tweet, which should solve this issue.

Comment 5 Steve Salevan 2010-02-16 21:29:28 UTC

Blocked by BZ #555091, pushing back to ON_DEV until unblocked.

Comment 6 wes hayutin 2010-02-17 13:27:10 UTC

mass move to rhq_chainsaw tracker bug

Comment 7 wes hayutin 2010-02-18 14:49:45 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 8 Steve Salevan 2010-03-09 20:14:20 UTC

VERIFIED on 5/9 master branch git pull.

Comment 9 wes hayutin 2010-03-10 14:19:34 UTC

moving verified bugs to rhq_sprint06, and removing from rhq_chainsaw

Comment 13 Corey Welton 2010-08-12 16:51:35 UTC

Mass-closure of verified bugs against JON.