Issue #4850 has been updated by Markus Roberts. Status changed from Unreviewed to Needs more information
I'm not at all clear on what specifically you are reporting as a problem. A few thoughts / questions: * Schedule can only prevent a resource from running; it can't guarantee that it will run (see http://docs.puppetlabs.com/guides/types/schedule.html) * I'm not sure why you included the cached catalog * Do you see the same issue without the $projects business? * Do you see the same issue using a notify directly (without the define)? * If you ran the client server version in the same timeframe as the apply, I would not expect it to have done the notify (it's outside the range). Could you perhaps offer some more information as to what you were expecting, what you saw instead, and why you feel it was incorrect? ---------------------------------------- Bug #4850: Schedule does not always work as expected when executed via puppetmaster/client http://projects.puppetlabs.com/issues/4850 Author: Chuck Schweizer Status: Needs more information Priority: Normal Assignee: Category: Target version: Affected version: 2.6.1 Keywords: Branch: The following code works correctly when run on a puppet client via "puppet apply". But if the same code is used from a puppetmaster it does not follow the schedule. class mynotify { $projects="TEST" schedule { sched_15to20: period => daily, range => "15 - 20", repeat => 48; } if ($projects) { mynotify::myproject { $projects: schedule => "sched_15to20"; } } define myproject() { notify { "found $name": } } } Here is the output when run from a puppet master $ date Mon Sep 27 11:12:44 CDT 2010 $ puppet apply -v --test info: Retrieving plugin info: Caching catalog for puppetcleint1 info: Applying configuration version '1285603757' notice: found TEST notice: /Stage[main]/Mynotify/Mynotify::Myproject[TEST]/Notify[found TEST]/message: defined 'message' as 'found TEST' notice: Finished catalog run in 7.65 seconds This message does not produce output if run via puppet apply - &id131 !ruby/object:Puppet::Relationship source: *id012 target: &id017 !ruby/object:Puppet::Resource catalog: *id001 exported: false file: /var/opt/puppet/environments/os_test_env/modules/mynotify/manifests/init.pp line: 9 parameters: !ruby/sym range: 15 - 20 !ruby/sym repeat: "48" !ruby/sym period: daily tags: - schedule - sched_15to20 - class - mynotify - node - basenode title: sched_15to20 type: Schedule - &id135 !ruby/object:Puppet::Relationship source: *id012 target: &id013 !ruby/object:Puppet::Resource catalog: *id001 exported: false file: /var/opt/puppet/environments/os_test_env/modules/mynotify/manifests/init.pp line: 14 parameters: !ruby/sym schedule: sched_15to20 tags: - mynotify::myproject - mynotify - myproject - test - class - node - basenode title: TEST type: Mynotify::Myproject -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
