Bug 869719 - Availability check change is not automatically picked up
Summary: Availability check change is not automatically picked up
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-24 15:42 UTC by bkramer
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of: 869716
: 869716 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description bkramer 2012-10-24 15:42:56 UTC
Description of problem:
When Availability check is changed, for instance from enabled to disabled, this change is not picked up by the agent and availability is still checked and server status changed depending on it's real state. 


Version-Release number of selected component (if applicable):
JON 3.1.0

How reproducible:
Every time.

Steps to Reproduce:
1. Import JBoss instance;
2. Navigate to Monitor -> Schedule (for that server instance) and disable Availability check;
3. After some time (at least 2 minutes if Availability check was initially set to 1 minute), stop the JBoss instance;
4. Execute "avail --force" on the JON Agent command line;
5. Check the status of the JBoss server;
  
Actual results:
The status of the JBoss instance changes to DOWN in JON UI. 

Expected results:
JBoss stays UP because it picks up the status of its parent resource (platform) as explained in [1]. 

Additional info:
The change in Availability check will be propagated after the agent is restarted with "--purgedata" option.

[1] https://access.redhat.com/knowledge/docs/en-US/JBoss_Operations_Network/3.1/html-single/Admin_Setting_up_Monitoring_Alerts_and_Operations/index.html#avail-backfill


Note You need to log in before you can comment on or make changes to this bug.