Issue #2251 has been updated by Nigel Kersten. Subject changed from cron doesn't clean crontab when changing user to cron provider doesn't correctly employ user property for resource existence checks.
user is actually a property of the provider, not a parameter, so we're not going to be automatically cleaning up crontab entries when you change user. Think of packages. When you change a resource to install 'foo' rather than 'bar', we don't uninstall 'bar'. There's definitely a bug here though, which I believe is captured by RI's update in note 4. ---------------------------------------- Bug #2251: cron provider doesn't correctly employ user property for resource existence checks. https://projects.puppetlabs.com/issues/2251 Author: Marc Fournier Status: Accepted Priority: Normal Assignee: Category: cron Target version: 2.6.x Affected Puppet 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://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.
