Bug 616661
| Summary: | Alert mapping for email addresses not quite right from 2.3.1 -> 2.4 -- off-by-ones? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Corey Welton <cwelton> | ||||||||
| Component: | Alerts | Assignee: | Joseph Marques <jmarques> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | 1.3 | CC: | jmarques, rtimaniy | ||||||||
| 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:59:57 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: | 601949, 614432 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 433294 [details]
alert2
Created attachment 433295 [details]
alert 3 - notification lists
Created attachment 433296 [details]
alert 3 - notification actions
commit 1d25a6cec3aa71897ad109ddcad0cade752ae289
Author: Joseph Marques <joseph>
Date: Wed Jul 21 01:39:06 2010 -0400
BZ-616661: keep alert notifications sticky to the definitions that defined them
* was incrementing the definitionId counter before persisting the configuration
* stop adding leading/trailing ',' to email-based notifications
** this would only occur when multiple notifications were defined for an alert definition
** if an alert definition would only have email-based notifications, the upgrade did not add the extra ','
*** Bug 616837 has been marked as a duplicate of this bug. *** QA Verified, extra commas are gone and alert notifications line up with their corresponding alerts. Mass-closure of verified bugs against JON. |
Description of problem: Fields from some alerts are getting comingled/moved over to other alerts, following an upgrade. Something is not being parsed right. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Created 3 alerts in jon 2.3.1: * "Alert1": Linux Platform Memory > 0.1B Notification method: cwelton+alert1 * "Alert2" JBoss AS JVM Availability DOWN Notification Method: cwelton+alert2 * "Alert3" RHQ Agent JVM Active Threads > -1.0 Notification Method: Notify Roles (All Resources Role, Super User Role) Notify JON Users (username - rhqadmin) cwelton+alert3 2. Shutdown server, upgrade to 2.4 3. After server is up and running, Subsystem Views > Alert Definitions 4. Click on each alert name and scroll to "Notification Actions"; note count. 5. Click "Edit" in "Notification Actions" for each; examine notifications Actual results: For the scenario above, we would expect Alert1 to have 1 action Alert2 to have 1 action Alert 3 to have 3 actions Expected results: Alert1 has 0 action Alert2 has 1 action Alert3 has 4 actions Furthermore, the email addresses do not match up appropriately for each Alert, and are pre-pended/appended with commas [see forthcoming screenshot]. Additional info: