Issue #3924 has been updated by Sergio Ballestrero.
Confirmed in puppet 2.7.17. This is very annoying when using tidy for configuration files, with daemons that require an explicit reload/restart, e.g. monit. ---------------------------------------- Bug #3924: Tidy can not trigger resources https://projects.puppetlabs.com/issues/3924#change-97524 * Author: Jan Doleschal * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: 3.x * Affected Puppet version: 0.25.4 * Keywords: * Branch: ---------------------------------------- Hello all, got a strange issue - tidy does not notify resources. <pre> tidy {"messages": path => "/var/log", size => "10m", matches => [ "zmd-messages.log.*", "zypper.log-*"] age => "30d", recurse => "true", backup => "false", rmdirs => "true", notify => Exec["restart_syslog"]; } exec {"restart_syslog": command => "/etc/init.d/syslog restart", refreshonly => true; } </pre> This should clean all matching Files in /var/log and execute restart_syslog, only if it gets triggered from tidy messages, or? But the exec is ignored. Jan -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
