Bug 751912

Summary:	Report missing base directory as out of compliance
Product:	[Other] RHQ Project	Reporter:	John Sanda <jsanda>
Component:	drift	Assignee:	John Sanda <jsanda>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	4.2
Target Milestone:	---
Target Release:	JON 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		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:	751454, 751474

Description John Sanda 2011-11-08 02:28:51 UTC

Description of problem:
When a drift definition is created with a base directory that does not exist, the definition should be flagged as being out of compliance. The definitions view for the resource should indicate that the definition is out of compliance.

If the base directory is later created during the life time of the definition, then the definition should be 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:32:26 UTC

Added support for flagging definitions as out of compliance when they are
created with a base directory that does not exist. If and when the base
directory is created the definition is updated as being back in compliance.


master commit hash:         efcd91eb5e853e3aaf21d45bf92a966bb460c34d
release_jon3.x commit hash: 34011a3bf7c201f67d33ed345138254b7bab835e

Comment 2 Mike Foley 2011-11-08 15:29:15 UTC

verified release_jon3 branch.  created a drift configuration on a non-existent directory.  showed out of compliance.

Comment 3 John Sanda 2011-11-11 22:33:47 UTC

*** Bug 736204 has been marked as a duplicate of this bug. ***

Comment 4 Mike Foley 2012-02-07 19:25:33 UTC

marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE

Comment 5 Mike Foley 2012-02-07 19:25:44 UTC

changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE