Jira (PUP-1585) cron resrouces with target specified generate duplicate entries

[Doug Forster (JIRA)]

Title: Message Title

Doug Forster created an issue   Puppet / PUP-1585 cron resrouces with target specified generate duplicate entries Issue Type: Bug Affects Versions: 3.4.2 Assignee: Eric Sorenson Created: 04/Feb/14 3:55 PM Environment: Debian GNU/Linux 7.2 (wheezy) Priority: Normal Reporter: Doug Forster The following resource results in duplicate cron entry added with each puppet run: cron { 'bacula_vacuumdb': ensure => present, minute => '00', hour => '12', command => 'vacuumdb --analyze -U postgres bacula', target => 'postgres', } Example of Cron: ~# crontab -l -u postgres # HEADER: This file was autogenerated at 2014-02-04 16:30:20 -0700 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 # Puppet Name: bacula_vacuumdb 0 12 * * * vacuumdb --analyze -U postgres bacula 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.