Issue #2251 has been updated by R.I. Pienaar aka Volcane.
Ran into the same, except its even worse in that it leaves the cronjob in the original users crontab, adds it to the new users cron tab. Then each time it runs puppet it does it again: Oct 6 09:16:16 box puppetd[3015]: (//Node[box.foo.com]/cron::oneoffcrons/Cron[cleanemail]/target) target changed 'nobody' to 'root' Oct 6 09:45:16 box puppetd[5545]: (//Node[box.foo.com]/cron::oneoffcrons/Cron[cleanemail]/user) user changed 'nobody' to 'root' End result was 260+ cron jobs all the same in the root users crontab. ---------------------------------------- Bug #2251: cron doesn't clean crontab when changing user http://projects.reductivelabs.com/issues/2251 Author: Marc Fournier Status: Accepted Priority: Normal Assigned to: Category: cron Target version: Affected version: 0.24.8 Keywords: cron Branch: If I change the "user" parameter of a cron{} resource, the previous user will still have the cron listed in his crontab. Assuming the resource name stays the same, I would have expected changing the "user" parameter to be as transparent as changing "hour", "minute", etc. This is a possible workaround, but it may not be desirable in every case: <pre> resource { "cron": purge => true } </pre> -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
