The redhat provider for the service type does indeed use chkconfig to
disable the service when
enable is false. If that's not happening for you, there's something wrong.

Some possibilities:
  * facter is misidentifying the OS, causing puppet to pick a different
default provider. Does
    'facter osfamily' return 'RedHat' or something else?
  * Someone's set an explicit default for the service type at top or node
scope which is overriding
    the default use of the redhat provider
  * chkconfig, for whatever reason, isn't actually disabling the service
when puppet calls it
  * Something else is re-enabling the service behind puppet's back

-Mike



On Wed, Sep 11, 2013 at 3:24 PM, Forrie <for...@gmail.com> 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?
>
>
> Thanks!
>
>  --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to