With agent down: 1) Create a drift definition with a missing or invalid base directory 2) Try to start agent The agent will not start up do to exceptions thrown in the drift sync.
As this is already fixed in master, and easy to test, please push to the release branch, and set to on-qa
I confirm this is fixed in master. I created a drift definition with a non-existence file path and I see this in the agent log but the agent started up fine otherwise: 2011-11-30 11:30:42,268 WARN [pool-3-thread-1] (rhq.core.pc.drift.DriftDetector)- The base directory [/this/is/bogus/foo] for DriftDetectionSchedule[resourceId: 10001, driftDefinitionId: 0, driftDefinitionName: Template-File System] does not exist. You may want review the drift definition and verify that the value of the base directory is in fact correct. It is not documented which git commit sha this was that fixed this. Someone needs to find it and cherry pick it over to the release branch.
master commit 8939b50bf8bee6f4b0037885026abdcd2f79946a -- verified by mazz (see above)
cherry picked to release branch: dee518db2b8c61813bf1cdad229f6388c0c4ec61
Verified on JON3-CR4 build. Created a drift definition with invalid base directory when agent is down. Started the agent. The agent is started successfully and the agent log displays below: 2011-12-01 17:15:39,636 WARN [pool-9-thread-1] (rhq.core.pc.drift.DriftDetector)- The base directory [/stores/tests] for DriftDetectionSchedule[resourceId: 10001, driftDefinitionId: 0, driftDefinitionName: Def1-Template-File System] does not exist. You may want review the drift definition and verify that the value of the base directory is in fact correct.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE