Jira (PUP-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title Kylo Ginsberg commented on PUP-5345 Re: SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404 Closing this one as a dup. Thanks for the quick response William Hopper! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title Joshua Partlow commented on PUP-5345 Re: SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404 Hooray! Thanks Will. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title
William Hopper commented on PUP-5345
Re: SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Joshua Partlow the good news is that the changes that went into puppet#master for PUP-5016 (specifically https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016) look to resolve this issue.
I was able to reproduce your exact issue on puppet agent 1.2.5, and then patched it with the new code. By default, we see:
root@jhgx2dg9wmcux3n:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service# puppet resource service puppet --param provider
service { 'puppet':
ensure => 'running',
enable => 'true',
provider => 'debian',
}
When enabling and disabling, we still use the upstart provider:
root@jhgx2dg9wmcux3n:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service# puppet resource service puppet enable=false --param provider
Jira (PUP-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title Joshua Partlow created an issue Puppet / PUP-5345 SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404 Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/10/08 10:47 AM Priority: Normal Reporter: Joshua Partlow This is probably very similar to PUP-5016 but with a different set of defaults. On Ubuntu platforms defaulting to upstart, a sysv init script ends up using the init rather than the debian provider, and therefore will not show the enable parameter when using `puppet resource service`. (Unless the 'enable' parameter is specifically set, see below) For example, on Ubuntu1404, with puppet-agent 1.2.2 installed: root@pe-201520-agent:/home/vagrant# puppet resource service puppet
