Jira (PUP-1370) when init scripts have been ported to upstart puppet does not detect service that are not working

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: when init scripts have been ported to upstart puppet does not detect service that are not working I stumbled across this issue while looking at the behavior in https://github.com/puppetlabs/puppet/pull/2276, and I don't know if this is still an issue: root@ubuntu-server-10044-x64-vbox4210-nocm:~# apt-cache policy mysql-server mysql-server: Installed: 5.1.73-0ubuntu0.10.04.1 Candidate: 5.1.73-0ubuntu0.10.04.1 Version table: *** 5.1.73-0ubuntu0.10.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 5.1.41-3ubuntu12.10 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 5.1.41-3ubuntu12.7 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 5.1.41-3ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages root@ubuntu-server-10044-x64-vbox4210-nocm:~# /etc/init.d/mysql status Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql status Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the status(8) utility, e.g. status mysql mysql stop/waiting root@ubuntu-server-10044-x64-vbox4210-nocm:~# echo $? 0 root@ubuntu-server-10044-x64-vbox4210-nocm:~# service mysql status mysql stop/waiting root@ubuntu-server-10044-x64-vbox4210-nocm:~# echo $? 0 root@ubuntu-server-10044-x64-vbox4210-nocm:~# puppet resource service mysql service { 'mysql': ensure => 'stopped', enable => 'true', } root@ubuntu-server-10044-x64-vbox4210-nocm:~# service mysql start mysql start/running, process 3616 root@ubuntu-server-10044-x64-vbox4210-nocm:~# service mysql status mysql start/running, process 3616 root@ubuntu-server-10044-x64-vbox4210-nocm:~# puppet resource service mysql service { 'mysql': ensure => 'running', enable => 'true', } Upstart does have a compatibility layer with legacy init scripts, as demonstrated with the following: root@ubuntu-server-10044-x64-vbox4210-nocm:~# service ntp start * Starting NTP server ntpd [ OK ] root@ubuntu-server-10044-x64-vbox4210-nocm:~# cat ntp.pp service { 'ntp': ensure => stopped, provider => upstart, } root@ubuntu-server-10044-x64-vbox4210-nocm:~# puppet apply ntp.pp Notice: Compiled catalog for ubuntu-server-10044-x64-vbox4210-nocm.vm in environment production in 0.04 seconds Notice: /Stage[main]/Main/Service[ntp]/ensure: ensure changed 'running' to 'stopped' Notice: Finished catalog run in 0.04 seconds While I don't know if this is still broken (and given the above it looks to be resolved) I think that removing the defaultfor statement on Ubuntu in the given PR will definitely solve the issue. If anyone is interested in this issue it would be helpful to get more verification cases. Add Comment   Puppet / PUP-1370 when init scripts have been ported to upstart puppet does not detect service that are not working I do not believe that this is a regresson and it was observed on 2.7.12 when a init script has been disabled, the following message is printed to stdout: <pre> root@db:~# /etc/init.d/mysql status Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql status Since the script you are attempting to i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.