I used to use Mcollective to orchestrate puppet updates but I have since drifted away from installing MCO in my environments seeing that it seems fairly inactive and causes its own problems (random nodes dropping out in a large virtual machine environment) curious as to how others have solved this with a high effective success rate.
-byron On Thursday, October 2, 2014 9:07:42 AM UTC-5, JonY wrote: > > I've been having problems (documented here) with upgrading my clients from > p-ver 3.5.1 and facter 1.7.5 to 3.7 and 2.2 respectively. (TL;DR - the > client gives a facter error with every run and is essentially wedged). > > I filed a bug but was told "restarting the puppet service will clear up > this error". Ok - that's great. But how? > > I tried adding this line to my puppet agent manifest (in the agent > 'service' definition): restart => '/usr/bin/nohup /etc/init.d/puppet > restart &'. My hope was that bouncing the client wouldn't interfere with > the running of said client. No dice. > > Supposedly the client will restart if there is a change to the puppet.conf > file - truth? Do I need to add some bogus values to prod the client into > action? > > Other suggestions? > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/39c8571b-6b57-4282-a3a5-15c5b06e4a8b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
