Issue #15797 has been updated by Chuck Schweizer.
This change is not working very well on RHEL 6. It seems a lot of chkconfig
entries are using a - for their run level, including Puppet's init
scripts. When the chkconfig is called with reset it disables the service.
httpd:# chkconfig: - 85 15
kdump:# chkconfig: - 20 80
ktune:# chkconfig: - 27 99
netconsole:# chkconfig: - 50 50
nfs:# chkconfig: - 30 60
nscd:# chkconfig: - 30 74
nslcd:# chkconfig: - 12 88
ntpd:# chkconfig: - 58 74
ntpdate:# chkconfig: - 57 75
psacct:# chkconfig: - 90 10
puppet:# chkconfig: - 98 02
puppetmaster:# chkconfig: - 65 45
puppetqueue:# chkconfig: - 65 45
rdisc:# chkconfig: - 41 89
rngd:# chkconfig: - 13 99
rpcsvcgssd:# chkconfig: - 31 69
saslauthd:# chkconfig: - 65 10
smartd:# chkconfig: - 99 01
svnserve:# chkconfig: - 85 15
tuned:# chkconfig: - 86 15
# chkconfig --list puppet
puppet 0:off 1:off 2:on 3:on 4:on 5:on 6:off
# chkconfig puppet off
# chkconfig --list puppet
puppet 0:off 1:off 2:off 3:off 4:off 5:off 6:off
# chkconfig puppet reset
# chkconfig --list puppet
puppet 0:off 1:off 2:off 3:off 4:off 5:off 6:off
# chkconfig puppet on
# chkconfig --list puppet
puppet 0:off 1:off 2:on 3:on 4:on 5:on 6:off
# chkconfig puppet reset
# chkconfig --list puppet
puppet 0:off 1:off 2:off 3:off 4:off 5:off 6:off
----------------------------------------
Bug #15797: Redhat service provider does not respect chkconfig header for
setting runlevels
https://projects.puppetlabs.com/issues/15797#change-70156
Author: Wade Brown
Status: Merged - Pending Release
Priority: Normal
Assignee: Jeff McCune
Category: service
Target version: 2.7.20
Affected Puppet version: 2.7.18
Keywords:
Branch: ‘https://github.com/puppetlabs/puppet/pull/1057
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.
