Issue #19716 has been updated by Matthaus Owens.
Released in Puppet 3.2.0-rc1 ---------------------------------------- Bug #19716: cron job not sucked into puppet https://projects.puppetlabs.com/issues/19716#change-89576 * Author: L Harris * Status: Closed * Priority: Normal * Assignee: * Category: cron * Target version: 3.2.0 * Affected Puppet version: development * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1528 ---------------------------------------- According to http://docs.puppetlabs.com/references/3.0.1/type.html#cron "If you specify a cron job that matches an existing job in every way except name, then the jobs will be considered equivalent and the new name will be permanently associated with that job. Once this association is made and synced to disk, you can then manage the job normally (e.g., change the schedule of the job)." existing job in root's crontab: 1 22 * * * /opt/novell/ExpirationNotification/expires.sh puppet manifest cron { "expires": command => "/opt/novell/ExpirationNotification/expires.sh", user => "root", hour => 22, minute => 1, require => File["/opt/novell/ExpirationNotification/expires.sh"], } running puppet results in puppet knowing not to change the job (or to add a 2nd one), but doesn't assign it a name. So when you do change something about the job (in my case the run time) it creates a 2nd job. -- 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.
