Issue #16809 has been updated by Matthaus Owens.
Released in Puppet 3.2.0-rc1 ---------------------------------------- Bug #16809: cron resource can destroy other resources https://projects.puppetlabs.com/issues/16809#change-89545 * Author: Stefan Schulte * Status: Closed * Priority: Normal * Assignee: * Category: cron * Target version: 3.2.0 * Affected Puppet version: * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1216 ---------------------------------------- I'm currently writing tests for the cronprovider and found an issue when removing an entry that has no title. I have the following crontab: <pre> @daily /bin/unnamed # Puppet Name: named_job @monthly /bin/named </pre> and the following manifest: <pre> cron { 'matched_by_command': command => '/bin/unnamed', special => 'daily', ensure => present, } </pre> If I apply the catalog nothing happens, because the resource can be matched again the first cronentry (command and special are the same). If I now switch ensure to `absent` I would expect puppet to create the following crontab: <pre> # Puppet Name: named_job @monthly /bin/named </pre> however, the actual result: <pre> @monthly /bin/named </pre> so the cronprovider may destroy the title (and also any environment variables between the title and the actual cronentry) of the following cronentrie when removing an entry. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
