Issue #15797 has been updated by Wade Brown.
`chkconfig off` sets levels 2-5, so if your chkconfig header tweaked 0, 1 or 6 (unlikely but possible), off would leave those intact. To be absolutely sure a service is disabled, you'd need to do `chkconfig <service> off --levels 0123456` ---------------------------------------- Bug #15797: Redhat service provider does not respect chkconfig header for setting runlevels https://projects.puppetlabs.com/issues/15797#change-68329 Author: Wade Brown Status: Unreviewed Priority: Normal Assignee: Category: service Target version: Affected Puppet version: 2.7.18 Keywords: Branch: This is essentially a repeat of #528, but the behavior it fixed has resurfaced. The command chkconfig <service> on Sets the service to be on in run levels 2-5. However, chkconfig supports a header to define what run levels to enable itself on, and that is instead triggered by the command chkconfig <service> reset The comments in puppet/provider/service/redhat.rb suggest that the header behavior should be respected, but the actual code passes :on, instead of :reset. # Don't support them specifying runlevels; always use the runlevels # in the init scripts. def enable output = chkconfig(@resource[:name], :on) rescue Puppet::ExecutionFailure => detail raise Puppet::Error, "Could not enable #{self.name}: #{detail}" end -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. 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-bugs?hl=en.
