Bug 1019941
Summary: | Only one availability duration alert can be triggered per resource due to non-unique scheduler trigger name/group | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Larry O'Leary <loleary> | |
Component: | Monitoring - Alerts | Assignee: | Jay Shaughnessy <jshaughn> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | JON 3.1.2, JON 3.2 | CC: | fbrychta, jshaughn | |
Target Milestone: | ER07 | |||
Target Release: | JON 3.2.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1028527 (view as bug list) | Environment: | ||
Last Closed: | Type: | Bug | ||
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: | 888927 | |||
Bug Blocks: | 1012435, 1028526, 1028527 |
Description
Larry O'Leary
2013-10-16 16:28:51 UTC
I updated the title as this issue does only apply to a resource that may have two or more availability duration conditions defined. But it also applies to a resource with a single availability duration applied if the resource's availability changes to meet the condition and then changes to something else and back again to meet the condition a second time before the first duration has expired. For example: Goes Down for 10 minutes --> went down for 1 minutes --> went up for 5 minutes --> went down for 15 minutes In this case, the second "went down" would result in the exception mentioned in comment #0 due to the duplicate availability duration jobs running on the same resource. The release branch is not open for 3.2.1 Target as 3.2.0 is still underway. So, leaving as ASSIGNED and recording only the push to master. master commit b3ac322d1538d4e2789cdc85a4cb3358fddb6758 Author: Jay Shaughnessy <jshaughn> Date: Fri Nov 8 09:07:18 2013 -0500 Fix this assumption by making the trigger name more unique: add a timestamp. release/jon3.2.x commit f4e76421928f54684f8d3dff14a6c4ca16a3ce4a Author: Jay Shaughnessy <jshaughn> Date: Wed Nov 13 10:17:44 2013 -0500 Fix this assumption by making the trigger name more unique: add a timestamp. Cherry-Pick master: b3ac322d1538d4e2789cdc85a4cb3358fddb6758 Test Case: As a note, the move from quartz trigger to EJB Timer (Bug 1030108) makes this fix somewhat irrelevant. But to ensure the use case still works the test case should be executed. Pick any resource you can easily cycle. AD-1: "Stays Down" - Stays Down for 5 minutes Bring down the resource and wait for the avail to change (sitting in the resource detail view is useful, that generates the 15s checks and quickly shows the change). - this will start the 5 minute timer Bring up the resource and wait for the avail to change Bring down the resource (again) and leave it down There should be: - no error generated in the server log - no alert for the first down event (because it didn't stay down) - an alert for the second down event (after 5 minutes fro the second shutown) Moving to ON_QA as available for testing with new brew build. Mass moving all of these from ER6 to target milestone ER07 since the ER6 build was bad and QE was halted for the same reason. |