Bug 854807

Summary: Starting/Stopping AS instance doesn't immediately change availability status in UI
Product: [Other] RHQ Project Reporter: Charles Crouch <ccrouch>
Component: No ComponentAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: hbrock, hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-09 07:00:57 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:    
Bug Blocks: 854805    

Description Charles Crouch 2012-09-06 03:02:40 UTC 
Users typically have the expectation that availability checks will reflect AS servers going up or down IMMEDIATELY. Given that is not the case, we should think about how to indicate to the user that we are polling for avail and are not event driven, e.g. next to the Resource's availability badge we have a label saying:

    Polling every: <X>
    where <X> is taken from the availability schedule.

Another option which I believe we may have already investigated is triggering an availability scan as part of an operation. However I do not expect this will provide the IMMEDIATE feedback users expect, i.e. as soon as the start or stop operation has executed that the availability icon will be updated to match appropriately. However I don't view this as sufficient since this requires updates to any plugin to take advantage of this feature and also doesn't address out-of-band changes, e.g. someone stopping an AS instance via the terminal versus through JON.
Comment 1 Heiko W. Rupp 2013-12-09 07:00:57 UTC 
The new live avail feature in RHQ 4.9 should solve this issue.