Bug 798064

Summary: Drift detection follows symbolic links (possibly unexpectedly) ... consider documentation
Product: [Other] RHQ Project Reporter: Mike Foley <mfoley>
Component: DocumentationAssignee: Deon Ballard <dlackey>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0.1CC: hrupp
Target Milestone: ---   
Target Release: JON 3.0.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-21 23:14:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike Foley 2012-02-27 23:59:23 UTC
Description of problem:  Drift detection follows symbolic links (possibly unexpectedly) ... consider documentation


Version-Release number of selected component (if applicable):  JON 3.01


How reproducible: 100%


Steps to Reproduce:
1.  create a symbolic link, e.g.   ln -s  /my/other/directory  mylink
2.  create a drift definition with a base directory that contains the symbolic link
3.  wait for drift detection, or click the detect now button
  
Actual results:  drift follows the symbolic link ... and snapshot #0 contains the files in /my/other/directory.  


Expected results:   to be crystal clear...the actual behavior is the expected behavior ... after you think about it.  but ...initially, it wasn't.  i happened to have a lot of files in /my/other/directory ...and i was wondering why drift detection took so long.   if you have a lot of files in /my/other/directory you may not be aware that snapshot #0 will contain all the files in that directory.  therefore, i think this is possible documentation opportunity.


Additional info:

Comment 2 Deon Ballard 2012-06-21 23:14:13 UTC
Closing.