Issue #4241 has been updated by Robin Powell.
I'm sorry, I just realized that I only rely on this in the hour field, not the minute field. Having special behaviour for the minute field seems not very POLA to me, but it would at least explain what I'm seeing (and the apparent contradiction in http://projects.puppetlabs.com/issues/1453 ) -Robin ---------------------------------------- Bug #4241: Cron type behavior change https://projects.puppetlabs.com/issues/4241 Author: Cody Robertson Status: Accepted Priority: High Assignee: Markus Roberts Category: cron Target version: Affected Puppet version: 0.25.5 Keywords: Branch: I've recently re-deployed with a newer version (0.25.1 to 0.25.5) with the same cron configuration and I'm now getting different results The cron config in question: <pre> # From example http://docs.puppetlabs.com/references/stable/type.html cron { "command": command => "/bin/command", user => "root", hour => [0,12], } </pre> In my previous setup (0.25.1) this produced the following in the crontab: <pre> # Puppet Name: command 0 0,12 * * * /bin/command </pre> Which according to the examples in the documentation is correct. However in my 0.25.5 deployment it produces: <pre> # Puppet Name: command * 0,12 * * * /bin/command </pre> Clearly this will run every minute which is not the expected result. To fix this all you have to do is specify the __minute__ parameter however this seems like a potentially dangerous change (bug?). -- 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.
