Issue #19552 has been updated by Charlie Sharpsteen. Status changed from Accepted to Duplicate
Closing as a duplicate of #16809 which is now merged. ---------------------------------------- Bug #19552: Cron handles special schedules poorly https://projects.puppetlabs.com/issues/19552#change-87439 * Author: Felix Frank * Status: Duplicate * Priority: Normal * Assignee: Felix Frank * Category: cron * Target version: * Affected Puppet version: 2.6.17 * Keywords: cronfixit crontab * Branch: ---------------------------------------- The crontab provider is rather schizophrenic. When parsing crontabs from disk, lines with special schedules such as @reboot are treated as a whole different breed than regular numerically scheduled tasks. That is necessary due to the structure of Puppet::Util::Fileparsing. However, upon creating new resources, such special schedules are just special cases of regular crontabs. A conditional in the implementation allows it to be generated correctly in the crontab file. Here's where the schizophrenia kicks in: When *not* dealing with brand new resources, but parsed records instead, certain code paths are never entered, and regenerating the record in file fails miserably. Neither the record name nor environment lines are written. A fix is already in the works. -- 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.
