Issue #1100 has been updated by Jason Antman.
I agree with DisConnect. This is extremely frustrating, and doesn't seem to be documented ( i reference http://docs.puppetlabs.com/man/kick.html). The docs say "Trigger a puppet run". Especially with the name "kick", I take this to mean "now, immediate, forceful". IMHO this is completely useless for those of us who run with --splay, We *really* need a way to trigger runs immediately. Case in point: I just rolled out a new module in my "test" environment. I ended up typo-ing a variable name. 6 hosts pulled the new code, and promptly spit out errors, before I could get the fix pushed out. So... I wait half an hour for them to pull again? Or I have to SSH into each one and manually trigger a run? Because, since I'm using puppetd with splay, kick does absolutely nothing. ---------------------------------------- Feature #1100: client should not sleep for $splay_time when triggered by puppetrun https://projects.puppetlabs.com/issues/1100#change-56370 Author: Dave Alden Status: Tests Insufficient Priority: Normal Assignee: Category: unknown Target version: Telly Affected Puppet version: 0.24.4 Keywords: Branch: When a client is triggered by puppetrun, it still sleeps for $splay_time before running. I've hacked together a (probably incorrect) patch that is working for me for now. :) -- 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.
