Jira (PUP-1371) puppet cannot manage agent or master after update to puppet 3.2

[Jo Rhett (JIRA)]

Title: Message Title

Jo Rhett commented on an issue   Re: puppet cannot manage agent or master after update to puppet 3.2 I'd like to note that this problem remains. If someone needs to manage the puppet.conf file (e.g. EVERYONE) then you need to put something ridiculous like this in there: <% if( scope.lookupvar('::osfamily') == 'RedHat' ) then -%> rundir = /var/run/puppet <% end -%> Well, either that or punch a bunch of settings into Hiera based on operating system. This is a workaround that requires the end customer to bridge the gap between the product as shipped and the default init scripts for the operating system. It's pretty much a guaranteed problem for any heterogenous environment at least once. One would think we can do better. Add Comment   Puppet / PUP-1371 puppet cannot manage agent or master after update to puppet 3.2 When puppet is configured to manage it's own services it fails, due to broken init scripts for EL6 <pre> Notice: /Stage[main]/Puppet::Server/Service[puppetmaster]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Puppet::Server/Service[puppetmaster]: Unscheduling refresh on Service[puppetmaster] Notice: /Stage[main]/Puppet/Service[pup... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.