On Wednesday, December 12, 2012 6:13:41 PM UTC-5, Ryan Coleman wrote: > > > > > On Wed, Dec 12, 2012 at 10:57 AM, Ugo Bellavance <[email protected]<javascript:> > > wrote: > >> Hi, >> >> I've built a puppet module myself to manage puppet.conf and I use a >> subscribe for the service, so it restarts the client whenever puppet.conf >> changes. I think I shouldn't but I'd like to have a confirmation. > > The fact that foreman sees a failure upon a change in puppet.conf makes me >> think even more that I am wrong... > > > If the service was successfully restarted, it should register as a > successful change. That's normal behavior. Is that not what you see? > > Makes sense, but I think Foreman may have a way to determine whether the report is Applied, Restarted, Failed, Restart Failure, Skipped or Pending. Maybe it shows Failed because it doesn't see the "Finished catalog run in 0.64 seconds" at the end? I guess maybe I should ask to the Foreman group, but I was mostly wondering whether it was a good idea or not to restart puppet when changing puppet.conf.
Thanks, Ugo -- 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/-/0HW2jDtOobsJ. 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-users?hl=en.
