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:
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?
Alas, the username and password are still filled in after the first firing.
I can not reproduce this. the microblog sender is now logging the status id to system log upon sending.
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.
Blocked by BZ #555091, pushing back to ON_DEV until unblocked.
mass move to rhq_chainsaw tracker bug
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.
VERIFIED on 5/9 master branch git pull.
moving verified bugs to rhq_sprint06, and removing from rhq_chainsaw
Mass-closure of verified bugs against JON.