Bug 732102 - Drift detection does not resume after agent restart (with --cleanconfig)
Summary: Drift detection does not resume after agent restart (with --cleanconfig)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: drift
Version: 4.1
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 707225
TreeView+ depends on / blocked
 
Reported: 2011-08-19 19:29 UTC by Mike Foley
Modified: 2012-02-07 19:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Mike Foley 2011-08-19 19:29:18 UTC
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

Comment 1 John Sanda 2011-08-25 14:36:06 UTC
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.

Comment 2 John Sanda 2011-09-15 21:01:00 UTC
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

Comment 3 Mike Foley 2011-09-16 15:07:13 UTC
TCMS testcase added.

verified 09/16/2011 RHQ 4.1 daily build.

Comment 4 Mike Foley 2012-02-07 19:31:35 UTC
marking VERIFIED BZs to CLOSED/CURRENTRELEASE

Comment 5 Mike Foley 2012-02-07 19:31:37 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


Note You need to log in before you can comment on or make changes to this bug.