Description of problem: Drift detection does not resume after agent restart (with --cleanconfig)
Steps to Reproduce:
1. shutdown agent
2. edit a file that is in a folder being watched by drift detetection
3. restart agent with --cleanconfig
When the agent restarts, it does get resources' drift configuration during inventory sync; however, it does not get the corresponding drift detection schedule because those only exist on the agent. The impact of this is that restarting the agent with --cleanconfig means the schedule will be "reset". To be clear, this only impacts when the next scheduled detection will occur.
Code is now in place to support syncing drift configurations when the agent is started either with a purged local inventory or an existing local inventory.
commit hash: 6f788d1ec4e183b26483267e9653dada84ea2b1a
TCMS testcase added.
verified 09/16/2011 RHQ 4.1 daily build.
marking VERIFIED BZs to CLOSED/CURRENTRELEASE
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE