Bug 869716
Summary: | Availability check change is not automatically picked up | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> | |
Component: | Agent | Assignee: | Jay Shaughnessy <jshaughn> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | JON 3.1.0 | CC: | loleary, myarboro, skondkar | |
Target Milestone: | --- | |||
Target Release: | JON 3.1.2 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | 869719 | |||
: | 869719 871873 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-11 11:00:17 UTC | 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: | 871873 | |||
Bug Blocks: |
Description
bkramer
2012-10-24 15:39:23 UTC
The impact of this issue can be pretty bad. It prevents the update of a resource's availability check interval from being modified, enabled, or disabled. The workaround is to force an inventory sync but this is a manual process. One can either execute agent command: inventory --sync Or restart the agent with the --purgedata command-line argument or delete the agent's inventory.dat file. All workarounds are not really ideal considering they all require knowledge of this bug before updating availability metric collection schedules for inventoried resources. I see no reason not to CP this to 3.1.2: commit cf8b29cf05e6fc4fea5e175431bcee99c91e376a Author: Jay Shaughnessy <jshaughn> Date: Wed Dec 12 15:26:58 2012 -0500 Set availability schedule data if present in ResourceMeasurementScheduleRequest Cherry pick of master commit: 257e056801c29bc241b7c292008326be14faffb9 Moving to ON_QA as new build available to test with: https://brewweb.devel.redhat.com/buildinfo?buildID=247371 Verified on JON 3.1.2 ER5. Followed the steps and verified that after avail --force at agent command line, the JBoss instance remains UP in JON UI. |