Bug #6990

Rehabilitate cron provider

Added by Nigel Kersten about 1 year ago. Updated 9 months ago.

Status:Accepted Start date:04/06/2011
Priority:Urgent Due date:
Assignee:- % Done:

0%
Category:cron
Target version:-
Affected Puppet version: Branch:
Keywords:
Votes: 0

Description

This is a parent bug with multiple child bugs, all related to the cron provider.

Note that I’ve deliberately not set the target version here. We have what looks like a reasonably complicated situation that will require a technical decision.

From my superficial examination of these issues, I don’t believe we can easily fix these issues and maintain backwards compatibility with all desired previous behavior.

I would be more than happy to be proven wrong however. If we can, we should be targeting these fixes at 2.6.x as well as Statler, but if we need to break compatibility, I’d like to see us offer the fixed provider as a module people can choose to install on 2.6.x

I’m listing all the related issues here as I’m sure we have a set of related bugs who may have common solutions.

Related issues

blocked by Puppet - Bug #775: Cron resources being deleted still require a command. Closed
blocked by Puppet - Bug #4241: Cron type behavior change Closed 07/15/2010
blocked by Puppet - Bug #5752: Solaris 10 root crontab gets destroyed Accepted 01/03/2011
blocked by Puppet - Bug #656: cron entries with newlines keep being updated Accepted
blocked by Puppet - Bug #593: Puppet's cron type struggles with vixie-cron Accepted
blocked by Puppet - Bug #709: crontab type seems to detect the current environment line... Accepted
blocked by Puppet - Bug #1453: removing a cron parameter does not change the object Accepted 07/27/2008
blocked by Puppet - Bug #2251: cron provider doesn't correctly employ user property for ... Accepted 05/12/2009
blocked by Puppet - Bug #2462: cron resources default behaviour with no periods seems po... Closed 07/29/2009
blocked by Puppet - Bug #3010: Crontab entries using "special" parameter can't be conver... Accepted 01/06/2010
blocked by Puppet - Feature #3452: cron user should be autorequired Closed 03/30/2010
blocked by Puppet - Bug #3220: cron provider doesn't purge puppet-created cron resources... Accepted 02/19/2010
blocked by Puppet - Bug #3553: Cron resource with no time fields throws useless error me... Needs Decision 04/13/2010
blocked by Puppet - Bug #10063: cron resource violates resource ordering Accepted 10/13/2011
blocked by Puppet - Bug #14283: Solaris 11 cron provider oddities Investigating 05/02/2012

Also available in: Atom PDF