Bug 751913 - Report drift for a pinned definition as out of compliance
Summary: Report drift for a pinned definition as out of compliance
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: drift
Version: 4.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: JON 3.0.0
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 751474
TreeView+ depends on / blocked
 
Reported: 2011-11-08 02:37 UTC by John Sanda
Modified: 2012-02-07 19:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description John Sanda 2011-11-08 02:37:55 UTC 
Description of problem:
When a pinned definition has drift, the definition needs to be flagged as being out of compliance. The definitions view for the definition should indicate that the definition is out of compliance. An "In Compliance?" column should be added to the definitions view to indicate whether or not each definition is in compliance.

When the resource is updated such that it no longer has any drift, the definition should be set to being back in compliance. If the definition becomes unpinned, it should also set to being back in 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 John Sanda 2011-11-08 02:38:21 UTC 
Added support for viewing compliance in the drift definitions view at the
resource level

master branch commit hash:  fa55e1b11afb478de2273ac0a9ff0f649abb4001
release_jon3.x commit hash: cac994d7f026b03df8c8abf3b8209157489af7f7
Comment 2 Mike Foley 2011-11-08 16:05:29 UTC 
verified jon 3 branch
Comment 3 Mike Foley 2012-02-07 19:25:38 UTC 
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE
Comment 4 Mike Foley 2012-02-07 19:29:56 UTC 
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
Note You need to log in before you can comment on or make changes to this bug.