[Puppet Users] Re: Puppet and RH "chkconfig"

jcbollinger
2013-09-12T17:29:12Z

On Wednesday, September 11, 2013 5:24:51 PM UTC-5, Forrie
wrote:
>
> I''ve been trying to follow several threads around Google about
Puppet and
> it''s use (or non-use) of chkconfig on RH Linux.
>
> What prompted me to do this is I noticed that Puppet is, correctly,
> repeatedly logging that it is changing a services from ON to OFF.  Funny, I
> thought I had disabled that with:
>
>      service { "ip6tables":
>                 enable => false,
>                 ensure => stopped,
>      }
>
> Which certainly works, but it doesn''t disable the service (ie:
"chkconfig
> servicename off") -- it seems like there should be a provider that
> correctly integrates with the system "chkconfig" --  I realize
that not all
> init scripts honor that, and for that folks can do whatever.  This is a
> basic functionality of RH Linux that enables, adds, deletes and otherwise
> alters the levels of basic services.   Seems reasonable that Puppet could
> properly interact with it?
>
> We are up to Puppet 3.4.x now.   I''m simply asking here as I
didn''t seem
> to find a definitive answer - a lot of code snippets and suggestions, I
> just wonder if this is on-tap for improvement or if someone has another,
> perhaps clever approach to working with this?
>
>

The default Service provider for RH-family systems certainly does use
''chkconfig'' to disable services, and has done for as long as I
have been
involved with Puppet.  It is limited in that it will only enable/disable
for the current runlevel, but that is not usually a problem in practice.
You can check whether Puppet has done this by looking at the output of
''/sbin/chkconfig --list <servicename>''.  Note that
"disabling" a service
does not mean that it cannot run -- neither in Puppet DSL nor in chkconfig
-- it merely means that the service will not be automatically started when
the system boots.

That Puppet repeatedly logs service shutdowns on the same node means one of
two things:

   1. Something else keeps starting the service back up, or
   2. Puppet is being fooled about the service running.

Since you say that Puppet is *correctly* logging service shutdowns, I infer
that you must be running into (1).


John