You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Puppet Users
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.
Andy Parker
unread,
Oct 2, 2012, 4:37:13 PM10/2/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
On Tue, Oct 2, 2012 at 11:06 AM, Corby Wilson <cor...@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'
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
On Tue, Oct 2, 2012 at 9:06 PM, Corby Wilson <cor...@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.