Issue #15797 has been updated by R.I. Pienaar.
+1 to keeping on, I do not believe 'reset' is the correct behaviour either way. 'reset' will tell it to do whatever is in the comments of the rc script. So if the rc script has all off on all runlevels specifying on will not actually enable it, it will just reset it to all off. manpage says: <pre> The reset flag resets the on/off state for all runlevels for the service to whatever is specified in the init script in question </pre> This is not the same as on at all. >From the fedora guidelines @ >http://fedoraproject.org/wiki/Packaging:SysVInitScript#.23_Default-Start:_line <pre> Each Fedora SysV-style initscript which needs to start by default in any runlevel must include this line in the LSB Header, and it must match the list of runlevels defined for startup in the Chkconfig header. Only services which are really required for a vital system should define runlevels here. If the service does not start by default in any runlevel, this line should be omitted. </pre> In this case calling reset when you mean on will just mean the service will never be set to start. ---------------------------------------- Bug #15797: Redhat service provider does not respect chkconfig header for setting runlevels https://projects.puppetlabs.com/issues/15797#change-70403 Author: Wade Brown Status: Merged - Pending Release Priority: Normal Assignee: 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.
