I use the command "puppet kick" to do remote triggers of a 60 node cluster. In the new release (3.0) it deprecated the command and the command fails with: Error: Host lcms-dn1.aws.tie.noklab.net failed: Error 400 on SERVER: Could not find indirection ''run'' (I use Passenger on Apache) The web page it gives for reference: http://links.puppetlabs.com/puppet-kick-deprecation is a dummy to the deprecation bug. What are we supposed to use to remote trigger puppet reloads? -C -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/3YFhyVycpyYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
They recommend installing MCollective, which I''ve not tackled yet -- but it seems like overkill for basic needs that were met by simple "puppet kick". There are other options out there like Func, et al. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Andy Parker
2012-Oct-02 20:37 UTC
Re: [Puppet Users] Puppet 3.0 deprecates the kick command
On Tue, Oct 2, 2012 at 11:06 AM, Corby Wilson <corby10@gmail.com> wrote:> I use the command "puppet kick" to do remote triggers of a 60 node cluster. > In the new release (3.0) it deprecated the command and the command fails > with: > Error: Host lcms-dn1.aws.tie.noklab.net failed: Error 400 on SERVER: Could > not find indirection ''run''As Forrie points out, we''ve deprecated kick in favor of mcollective, or you can log into the box and run the agent directly. That it isn''t working is a bug. You can see a list of upgrade issues that we are tracking at http://projects.puppetlabs.com/projects/puppet/wiki/Telly_Upgrade_Issues and the issue with puppet kick being broken is specifically at http://projects.puppetlabs.com/issues/15717> > (I use Passenger on Apache) > > The web page it gives for reference: > http://links.puppetlabs.com/puppet-kick-deprecation > is a dummy to the deprecation bug. > > What are we supposed to use to remote trigger puppet reloads? > > -C > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/3YFhyVycpyYJ. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Miguel Di Ciurcio Filho
2012-Oct-02 23:24 UTC
Re: [Puppet Users] Re: Puppet 3.0 deprecates the kick command
On Tue, Oct 2, 2012 at 3:13 PM, Forrie <forrie@gmail.com> wrote:> They recommend installing MCollective, which I''ve not tackled yet -- > but it seems like overkill for basic needs that were met by simple > "puppet kick". There are other options out there like Func, et al. >I have raised this same point a few weeks ago at puppet-dev mailing list [1], when I saw the committed change. `puppet kick` is very handy and I think that deprecating it is kinda of an imposition made by PuppetLabs'' developers in favor of MCollective. [1] https://groups.google.com/d/topic/puppet-dev/P987lwK4AI0/discussion -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Andrei-Florian Staicu
2012-Oct-03 04:12 UTC
Re: [Puppet Users] Puppet 3.0 deprecates the kick command
On Tue, Oct 2, 2012 at 9:06 PM, Corby Wilson <corby10@gmail.com> wrote:> I use the command "puppet kick" to do remote triggers of a 60 node cluster. > In the new release (3.0) it deprecated the command and the command fails > with: > Error: Host lcms-dn1.aws.tie.noklab.net failed: Error 400 on SERVER: Could > not find indirection ''run'' > > (I use Passenger on Apache) > > The web page it gives for reference: > http://links.puppetlabs.com/puppet-kick-deprecation > is a dummy to the deprecation bug. > > What are we supposed to use to remote trigger puppet reloads? >I''ve dropped puppet kick (and even the agents) in favor of using pssh. If you use something like pssh -h clientlist -o out -e err "puppet agent --test" you can more easily browse the results afterwards. You can even set the parallelism, so you don''t choke the master or the network. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.