The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #14082

Ressource cron should set undefined attributes in crontab to * instead of leaving them untouched.

Added by Andreas John about 2 years ago. Updated about 1 year ago.

Status:DuplicateStart date:04/19/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Hi, if I have cron ressource like this:

cron{ "blah":
    command => 'blubb',
    user    => "root",
    hour    => "2",
    minute  => "0",
    weekday => "5",
    ensure  => "present",

}

and remove a property (e.g. weekday):

   cron{ "blah":
    command => 'blubb',
    user    => "root",
    hour    => "2",
    minute  => "0",

weekday => “5”,

    ensure  => "present",

}

I would expect puppet to set the weekday to “*”, but instead it leaves it untouched, i.e. it stays at “5” in my example.


Related issues

Duplicates Puppet - Bug #1453: removing a cron parameter does not change the object Closed 07/27/2008

History

#1 Updated by Daniel Pittman about 2 years ago

  • Status changed from Unreviewed to Needs Decision

I can see why both paths are attractive; we need a decision on how the model should work.

#2 Updated by Charlie Sharpsteen about 1 year ago

  • Status changed from Needs Decision to Duplicate

Closing as a duplicate of #1453.

Also available in: Atom PDF