Bug 751914

Summary: Add drift compliance to inventory summary report
Product: [Other] RHQ Project Reporter: John Sanda <jsanda>
Component: driftAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.2CC: loleary
Target Milestone: ---   
Target Release: JON 3.0.0, RHQ 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
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: 707225, 751474    
Attachments:
Description Flags
inventory summary report none

Description John Sanda 2011-11-08 02:43:04 UTC
Description of problem:
The inventory summary report should be updated to show the following:

* which types support drift monitoring
* which types have resources out of compliance
* which types have all resources in compliance

Drilling down on a particular type should show which resources are out of compliance. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jay Shaughnessy 2011-11-11 22:17:17 UTC
Should be working now. Please test.

Comment 2 Mike Foley 2011-11-14 15:55:41 UTC
Created attachment 533558 [details]
inventory summary report

Comment 3 Mike Foley 2011-11-14 15:57:47 UTC
verified as follows:

1) created simple drift defintion
2) viewed Reports-->Inventory Summary
3) observed entire "In Compliance?" column is blank

discussed with jsanda

documenting what i see and attaching screenshot to BZ

returning BZ to jsanda as this does not look right to me.

jsanda, can you describe what i should be seeing in the report for compliance when i have a pinned defintion?

Comment 4 Jay Shaughnessy 2011-11-15 03:34:15 UTC
master     commit 88aaa3b1ec22fd04ced1281db43c60a01e12f974
release3.x commit:  a8c48ad2e851ddbb4b03e7f802d5831b5aaab89a

test notes
For more on the definition of drift compliance see:
http://rhq-project.org/display/RHQ/Drift+Management#DriftManagement-Terminology

Comment 5 Mike Foley 2011-11-15 18:13:53 UTC
I am still not seeing anything in the "In Compliance?" column.  (  I did in the sprint 8 demo, but not in  the build).  I will retest again tomorrow in case the build I have didn't pick up this change.

Comment 6 Jay Shaughnessy 2011-11-16 16:42:03 UTC
Mike, sorry, the change did not get pushed to release branch as
noted above. It is there now:

release3.x commit 1facedce68f988d8b2905e0854f010f6fbdda441

Comment 7 Mike Foley 2011-11-16 16:56:05 UTC
i have retested on 11/16 in the release branch ... and still do not see anything.  i will again retest tomorrow.

Comment 8 Mike Foley 2011-11-17 15:42:19 UTC
verified 11/17 jon 3 branch

Comment 9 Larry O'Leary 2012-01-20 21:08:56 UTC
Part of the change for this was committed to master as part of http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=6a9ab0dfe846cdf9ae64e52d3a755ba9c8bd38ca

Comment 10 Mike Foley 2012-02-07 19:25:21 UTC
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE

Comment 11 Mike Foley 2012-02-07 19:29:20 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE