Issue #4107 has been updated by Fabrice Bacchella.
Is this ticket being rejected (as in comment 11) or scheduled for version 3 (as in comment 12) ? Any way, mcollective will be a good alternative to kick when [AgentPuppetd](http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/AgentPuppetd) will be ready and integrated. Now it just provided a minimal service as it can only run puppet with --onetime or send it signal USR1, no argument can be send like noop or tags. ---------------------------------------- Bug #4107: puppet kick ignores --noop, and it isn't clear what the correct behavior should be https://projects.puppetlabs.com/issues/4107#change-73651 Author: Jesse Wolfe Status: Rejected Priority: Normal Assignee: Category: Target version: 3.0.0 Affected Puppet version: 0.25.5 Keywords: Branch: puppet kick silently ignores --noop (and many other puppet configuration vars as well), but it isn't clear to me what the correct behavior of options to kick should be - should they affect the kick process or should they propagate to the remote machine for the duration of the run (see #864 and #3868)? -- 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.
