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

Feature #5856

Classes should support schedules

Added by Yuri Arabadji over 3 years ago. Updated over 1 year ago.

Status:AcceptedStart date:01/12/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

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

We've Moved!

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

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

  • It looks like schedules don’t work for classes. This is really sad. What I want here is just a simple propagation down to every defined resource in the class, but not past the other included classes.
schedule { 'once':
    period  => daily,
    repeat  => 1,
}

class ca {
    notify { 'RUN': }
}

node 'default' {
    class { 'ca': schedule => once }
}
  • The documentation needs to be updated for either types or metaparams or both and explicitly stated that schedule doesn’t apply to class resources (yet).
  • Make it clear in docs that “puppet apply” can’t honor schedules and that —ignoreschedules should be used to toggle the “[off]/[not working]” switch.

Thank you.

History

#1 Updated by James Turnbull over 3 years ago

  • Status changed from Unreviewed to Needs More Information
  1. What error did you receive?
  2. What version of Puppet is this?
  3. What platform is this?
  4. What Ruby version is this?

#2 Updated by Yuri Arabadji over 3 years ago

  • Target version set to 69
  1. no error. please change the category to “feature”, not “bug”.
  2. 2.6.4
  3. linux , centos 5.5
  4. 1.8.7

#3 Updated by James Turnbull about 3 years ago

  • Tracker changed from Bug to Feature
  • Status changed from Needs More Information to Needs Decision
  • Assignee set to Nigel Kersten

#4 Updated by James Turnbull about 3 years ago

  • Subject changed from "schedule" bugs to Schedule behaviour
  • Target version deleted (69)
  • Affected Puppet version set to 2.6.4

#5 Updated by Nigel Kersten about 3 years ago

Lets flesh this out a little more.

If you include a given class, confined to a given schedule, and it’s outside the schedule, what do you expect to see happen server and client side?

#6 Updated by Yuri Arabadji about 3 years ago

I expect the same behaviour as with tags, attached to a class. That is, they propagate down to resources.

Nigel Kersten wrote:

Lets flesh this out a little more.

If you include a given class, confined to a given schedule, and it’s outside the schedule, what do you expect to see happen server and client side?

#7 Updated by Nigel Kersten about 3 years ago

  • Subject changed from Schedule behaviour to Classes should support schedules
  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)
  • Target version set to 2.7.x

#8 Updated by Cody Herriges over 2 years ago

So what if something being affect by a schedule is an upstream dependency of a another resource? Do all other resources associated with that part of the graph fail when the class is outside of its schedule or do they assume that they are satisfied?

#9 Updated by Andrew Parker over 1 year ago

  • Target version deleted (2.7.x)

Also available in: Atom PDF