Description of problem: We need to provide some additional logging around drift detection so that we can better see the following: * when drift detection gets scheduled/requested * when drift detection ends (as a result of a drift configuration be deleted) * what is on the schedule queue Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I have added more detailed logging around the following: * adding a schedule for a drift configuration * removing a scheudle for a drift configuration * updating a drift configuration for an existing schedule Additional output is included when DEBUG is turned on. The agent logs will show what is in the schedule queue, and also report if it fails to update the queue. Failure to update the queue is reported with a WARN level so DEBUG is not required to see those statements. commit hash: 5d4fbbefb4f9ee8767e3fb8e18c87a95bdd80d79
attaching agent log file, which documents the verification of this BZ.
Created attachment 520872 [details] agent log file which documents verification
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE