Jira (PUP-1624) Cron handles crontab's equality of target and user strangely

[Felix Frank (JIRA)]

Title: Message Title

Felix Frank created an issue   Puppet / PUP-1624 Cron handles crontab's equality of target and user strangely Issue Type: Bug Affects Versions: 3.x Assignee: Felix Frank Components: Types and Providers Created: 09/Feb/14 12:27 PM Environment: Linux, probably *NIX, running as root Priority: Normal Reporter: Felix Frank When managing the target property of a cronjob, the user property uses its default instead (which is the user running puppet). To the crontab provider, these are basically the same, and there is code to handle them equally. Through the mixtures of defaults and actual supplied values, though, bizarre behaviors come up: # HEADER: This file was autogenerated at 2014-02-09 20:31:59 +0100 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: bacula_vacuumdb 0 12 * * * vacuumdb --analyze -U postgres bacula Running this manifest should not cause a sync: cron { 'bacula_vacuumdb': ensure => present, minute => '00', hour => '12', command => 'vacuumdb --analyze -U postgres bacula', target => 'ffrank', } But this happens: # RUBYLIB=lib puppet apply /tmp/target.pp /Stage[main]//Cron[bacula_vacuumdb]/user: user changed 'ffrank' to 'root' Finished catalog run in 0.39 seconds Note that this bug is currently masked by PUP-1585, which introduces an even worse misbehavior. Both will need to be fixed in unison. Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.