Issue #5414 has been updated by Eric Shamow. Priority changed from Normal to High
I'm seeing exactly the same problem in our environment. Even with every option on, including replace and purge, modified files are NOT detected. This really is a regression in behavior. ---------------------------------------- Bug #5414: file resource can't be used to monitor file changes recursively https://projects.puppetlabs.com/issues/5414 Author: Ben - Status: Unreviewed Priority: High Assignee: Category: file Target version: Affected Puppet version: 2.6.3 Keywords: Branch: for a long time i have used puppet to monitor a directory recursively for file changes but since upgrading to 2.6 that doesn't appear to work. # file_test.pp file { "/tmp/file_test": ensure => directory, recurse => true, checksum => mtime, mode => 644, notify => Exec["tar"]; } exec { "/bin/tar -cf - /tmp/file_test > /dev/null": alias => "tar", refreshonly => true; } Using the above manifest the following does not act as expected. puppet apply --verbose file_test.pp # creates /tmp/file_test and runs exec as expected mkdir /tmp/file_test/{1,2,3,4,5,6} puppet apply --verbose file_test.pp # does nothing, should run exec puppet apply --verbose file_test.pp # does nothing, should do nothing touch /tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15} puppet apply --verbose file_test.pp # does nothing, should run exec -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
