Issue #15797 has been updated by Jeff McCune. Status changed from In Topic Branch Pending Review to Tests Insufficient Assignee set to Jeff McCune Target version set to 2.7.x Branch set to ‘https://github.com/puppetlabs/puppet/pull/1057
New pull request that starts to add test coverage: <https://github.com/puppetlabs/puppet/pull/1057> ---------------------------------------- Bug #15797: Redhat service provider does not respect chkconfig header for setting runlevels https://projects.puppetlabs.com/issues/15797#change-69534 Author: Wade Brown Status: Tests Insufficient Priority: Normal Assignee: Jeff McCune Category: service Target version: 2.7.x 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.
