[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-11-05 Thread tickets
Issue #3010 has been updated by Andrew Parker. Released in 3.3.0 Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010#change-99518 * Author: Jesse Wolfe * Status: Clo

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-16 Thread tickets
Issue #3010 has been updated by Adrien Thebo. Target version changed from 3.x to 3.3.0 Merged into master in a042352; this should be released in 3.3.0. Thanks again! Bug #3010: Crontab entries using "special" parameter can't be converted to non-special

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-02 Thread tickets
Issue #3010 has been updated by Felix Frank. Have a pull :-) https://github.com/puppetlabs/puppet/pull/1577 See a head-scratcher in the comments there, but either way, this should be fit for merging. Bug #3010: Crontab entries using "special" paramete

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-02 Thread tickets
Issue #3010 has been updated by Felix Frank. Charlie Sharpsteen wrote: > With the release of 3.0.0, we adopted the Semantic Versioning spec. See > [semver.org](http://semver.org/) for a description of guidelines. I see. That makes sense then. I'll see about implementing the simple addition.

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-02 Thread tickets
Issue #3010 has been updated by Charlie Sharpsteen. Felix Frank wrote: > Charlie Sharpsteen wrote: > > Also, addressing this issue would tie into fixing #4820 which raises the > > issue that it is somewhat silly to be able to specify both normal and > > special schedules in a cron resource wit

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-01 Thread tickets
Issue #3010 has been updated by Felix Frank. Charlie Sharpsteen wrote: > Also, addressing this issue would tie into fixing #4820 which raises the > issue that it is somewhat silly to be able to specify both normal and special > schedules in a cron resource without Puppet raising a fuss. I had

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-01 Thread tickets
Issue #3010 has been updated by Charlie Sharpsteen. Also, addressing this issue would tie into fixing #4820 which raises the issue that it is somewhat silly to be able to specify both normal and special schedules in a cron resource without Puppet raising a fuss. --

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-01 Thread tickets
Issue #3010 has been updated by Charlie Sharpsteen. Felix Frank wrote: > Right. I'd be willing to make 'absent' a meaningful value for the special > property. Absolutely. It is definitely a bug that we can't currently specify `special => absent` to return a job from something like `@reboot` t

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-04-01 Thread tickets
Issue #3010 has been updated by Felix Frank. Right. I'd be willing to make 'absent' a meaningful value for the special property. But then, I'd like to even go further and introduce a logic like the following: If any numeric schedule has a should-value, and the special property does not have

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-03-29 Thread tickets
Issue #3010 has been updated by Charlie Sharpsteen. After pondering for a minute or two, I'm going to take a guess and say that what we're seeing here is Puppet's expected behavior where it won't flush unmanaged schedule entries. I.E. if you start out with following in a manifest: hour => 1

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-03-29 Thread tickets
Issue #3010 has been updated by Charlie Sharpsteen. This was not addressed by #16809, puppet still sends a Notify claiming that it is setting the minute schedule to 50 but never does. The schedule stays stuck on `@reboot`. The one improvement that was made is that the resulting crontab entry

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2013-03-19 Thread tickets
Issue #3010 has been updated by Felix Frank. This issue is addressed by #16809. It has a promising fix attached and its merge is pending. Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.pu

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2012-01-20 Thread tickets
Issue #3010 has been updated by Joshua Lifton. Description updated Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010 Author: Jesse Wolfe Status: Accepted Priority:

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2011-12-14 Thread tickets
Issue #3010 has been updated by Joshua Lifton. Updating tickets assigned to a former Puppet Labs employee. Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010 Author:

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2010-11-16 Thread tickets
Issue #3010 has been updated by James Turnbull. Target version deleted (0.25.6) Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries https://projects.puppetlabs.com/issues/3010 Author: Jesse Wolfe Status: Accept

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2010-04-13 Thread redmine
Issue #3010 has been updated by James Turnbull. Target version changed from 0.25.5 to 0.25.6 Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries http://projects.puppetlabs.com/issues/3010 Author: Jesse Wolfe St

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2010-01-13 Thread redmine
Issue #3010 has been updated by James Turnbull. Target version changed from Puppet - 0.25.4 to Puppet - 0.25.5 Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries http://projects.reductivelabs.com/issues/3010 A

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2010-01-07 Thread redmine
Issue #3010 has been updated by Markus Roberts. Target version changed from Puppet - 0.25.3 to Puppet - 0.25.4 Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries http://projects.reductivelabs.com/issues/3010 A

[Puppet - Bug #3010] Crontab entries using "special" parameter can't be converted to non-special entries

2010-01-05 Thread redmine
Issue #3010 has been updated by Jesse Wolfe. Target version set to Puppet - 0.25.3 Bug #3010: Crontab entries using "special" parameter can't be converted to non-special entries http://projects.reductivelabs.com/issues/3010 Author: Jesse Wolfe Status: U