Hi John,
Fix it. It was a Problem with the ruby version. Updated ruby from 1.8.7 to ruby 2.0 everything works fine now. I can only repeat myself, scheduled resources never gets applied. The other problem was that the old puppet option ignoreschedule ignored all schedules. With puppet 3.2.4 it is called ignoreschedules. Ignoreschedule must be called with a valid schedule name... . Thanks for helping Jan ______________________________________________________________ Jan Doleschal Landesamt für Geoinformation und Landentwicklung Baden-Württemberg (LGL) Abteilung 3 - Geodatenzentrum Ref. 31 Stuttgarter Straße 161 70806 Kornwestheim Tel.: +49 7154 9598 - 628 Fax: +7154 9598 -92- 628 E-Mail: jan.dolesc...@lgl.bwl.de http://www.lgl-bw.de <http://www.lgl-bw.de/> ______________________________________________________________ Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im Auftrag von jcbollinger Gesendet: Dienstag, 1. Oktober 2013 15:07 An: puppet-users@googlegroups.com Betreff: [Puppet Users] Re: Puppet ignores schedules On Tuesday, October 1, 2013 2:58:36 AM UTC-5, jamido wrote: Hi John, sorry for the late response - of course, schedules allow resources to be applied in the window. but after upgrading puppet from 0.25.4 to 3.2.4 some schedules are always ignored and resources gets never applied. It does not happen on all hosts ~250, only on some ~5. That is not what your log fragment depicts. It shows a schedule being obeyed, preventing the resource to which it is assigned from being applied. If the schedule were ignored then Puppet would not skip the resource. If this is happening with the manifest you presented in your initial post then I can think of only a few likely explanations: 1. You are applying the catalog outside the schedule window (02:00 - 04:00 AM, any day of the week). 2. You are applying the catalog twice within one schedule window. 3. Your nodes think you are applying the catalog outside the schedule window, even though you're not. With respect to (3), time synchronization does not usually present a problem because Puppet's SSL infrastructure prevents nodes from connecting to the master if their clocks are too far off. However, you might nevertheless have a time discrepancy if some of your nodes are configured with the wrong time zone. John -- You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/EwAA-WIvC0A/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
