Issue #6593 has been updated by James Turnbull. Status changed from Unreviewed to Duplicate
---------------------------------------- Bug #6593: Cron loses track of crontab easily, results in duplicates https://projects.puppetlabs.com/issues/6593 Author: Nick Moffitt Status: Duplicate Priority: Normal Assignee: Category: cron Target version: Affected Puppet version: 2.6.4 Keywords: cron duplicate crontab Branch: On a system with several root crontab entries modeled as `cron` resources, I took one out of my manifests as it was no longer needed. This of course did not remove the entry in the crontab, so I did a quick `cron { "name_of_old_entry": ensure => absent, }` to clear it out. Puppet then started spouting errors about lack of a `command` parameter, but kept running. I added the old entries back as they once were, this time with added `ensure=>absent` parameters, and was delighted to see them vanish. However, now several other entries appear to have been duplicated, like so: # HEADER: This file was autogenerated at Wed Mar 02 22:29:47 +0000 2011 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that the comments starting with 'Puppet Name' should # HEADER: not be deleted, as doing so could cause duplicate cron jobs. # Puppet Name: pullhaps */9 * * * * cd /var/lib/happening_clients/ && for i in *; do rsync -aq --delete $i::haps/ /var/lib/haps/$i/; done # Puppet Name: stuff_monitor 7,17,27,37,47,57 * * * * /usr/local/sbin/stuff-monitor # Puppet Name: check_zootboot 23 */3 * * * /usr/local/sbin/check-zootboot # Puppet Name: gubble_update_base 4,34 * * * * /usr/local/sbin/gubble-update base # Puppet Name: gubble_update_all 23 2 * * * /usr/local/sbin/gubble-update all # Puppet Name: lshw 10 23 * * * lshw -short -disable scsi > /var/lib/nagios/lshw.txt # Puppet Name: lshw 10 23 * * * lshw -short -disable scsi > /var/lib/nagios/lshw.txt # Puppet Name: gubble_update_base 4,34 * * * * /usr/local/sbin/gubble-update base # Puppet Name: gubble_update_all 23 2 * * * /usr/local/sbin/gubble-update all # Puppet Name: check_zootboot 23 */3 * * * /usr/local/sbin/check-zootboot Fortunately my scripts all have locks preventing collisions (except for that `lshw` up there, which is bothering me the most), but it generates a lot of spam mail from cron right now. I plan to delete the upper set manually and see if puppet recognizes the bottom ones as its own, but it's kind of confusing to me that puppet can't uniquely identify a crontab entry it made, interim syntax gaffe or no. -- 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.
