Issue #3010 has been updated by Charlie Sharpsteen.
After pondering for a minute or two, I'm going to take a guess and say that what we're seeing here is Puppet's expected behavior where it won't flush unmanaged schedule entries. I.E. if you start out with following in a manifest: <pre> hour => 1 </pre> Then remove that parameter, Puppet won't touch the hour component of the Cron entry. The component is simply "unmanaged" and Puppet won't mess with it until you explicitly tell it to manage differently: <pre> hour => '*' </pre> The problem with special schedules is that we currently don't have an equivalent of `*` that can be used to remove them. Ref: #1453, #19198 ---------------------------------------- Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010#change-87764 * Author: Jesse Wolfe * Status: Accepted * Priority: Normal * Assignee: * Category: cron * Target version: 3.x * Affected Puppet version: 0.25.2 * Keywords: * Branch: ---------------------------------------- A crontab entry created like so: <pre> cron{ "test": command => "/bin/echo > /tmp/puppet.txt", special => "reboot", } </pre> and then changed like so: <pre> cron{ "test": command => "/bin/echo > /tmp/puppet.txt", minute => 50 } </pre> will not change, and will show the notice: notice: //Cron[test]/minute: defined 'minute' as '50' on every run. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
