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:
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
verified release_jon3 branch. created a drift configuration on a non-existent directory. showed out of compliance.
*** Bug 736204 has been marked as a duplicate of this bug. ***
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE