This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 871936

Summary: Drift subsystem only providing limited amount of visual feedback
Product: [Other] RHQ Project Reporter: Charles Crouch <ccrouch>
Component: driftAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: hbrock
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: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 854805    

Description Charles Crouch 2012-10-31 14:34:40 EDT
I see two areas which could be improved here to make it clearer to users what is happening with the drift subsystem

1) when you visit the Resource Drift Detection Definition page, there is no indicator as to when the last drift detection event ran or when the next one is scheduled for. This would be helpful to set users expectations about whether a change on the filesystem should have been picked up by the drift detection
2) When you hit "Detect Now" button a message comes up saying the detection has been scheduled, but from then on there is no way to determine the progress or lack there of the detection, you just have to wait and see, if drift was found, the snapshot version # will increase. If no drift was found the snapshot version # won't increase and you won't know the drift completed.

For examples of these see http://people.redhat.com/~dowoods/subfolder/jon.ogv from 43minutes on.