The schedule resource has some behavior that comes across as a little...strange.
For example: * If you specify a range of "02:00:00 - 01:00:00", Puppet will fail with "Parameter range failed: Invalid range 02:00:00 - 01:00:00; ranges cannot span days.". * If you specify "01:30:00 - 01:00:00", then it is allowed and you get an info message stating "Assuming upper limit should be that time the next day". These seem completely contradictory (and the auto-conversion doesn't seem very useful given it looks like it will end up with a schedule that will _always_ allow application). There's another oddity in that if you don't specify the minutes/seconds then they will default to whatever the _current_ minutes/seconds are on the master. It seems like they should default to zero, instead. Given these things, it seems like we should remove the "Assuming upper limit should be that time the next day" behavior entirely, and defaulting the missing time components to zero instead of to whatever the current value is for the server. If these changes would break how you're using schedules, please let us know (here, or on the related ticket[1]) and please let us know why. [1] http://projects.puppetlabs.com/issues/7639 -- Jacob Helwig
signature.asc
Description: Digital signature
