[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Experiencing after update to 15.10 As upstart is replaced by systemd, I changed the /sbin/status to use the service command: #!/bin/bash /usr/sbin/service $1 status echo $? which solves the problem, just mentioned it if anyone wants to get puppet running anyway. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Experiencing this on 15.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
I also ran into that problem on 15.10 beta. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
This still exists in current dev-version of Ubuntu 15.10. Is this a bug caused by the (quite old, current Puppet-version is 4.2.2) Ubuntu package or by puppet itself? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Is this related to bug 1495853? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
** Changed in: puppet (Ubuntu) Assignee: (unassigned) => Ryan Harper (raharper) ** Changed in: puppet (Ubuntu Vivid) Assignee: (unassigned) => Ryan Harper (raharper) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
** Changed in: puppet (Ubuntu) Milestone: None => ubuntu-15.10 ** Also affects: puppet (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: puppet (Ubuntu Vivid) Status: New => Triaged ** Changed in: puppet (Ubuntu Vivid) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Thanks Stig. Looks like we want to cherry-pick relevant changes between 3.7.2-1 and 3.7.2-4. ** Changed in: puppet (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Correct behaviour (default to systemd, determine if it is running, fallback to upstart / sysvinit) seems to have been added to puppet upstream at 4.1.0-87-g7fe6164, just a few days ago. This looks like it will be part of the puppet 4.1.1 release. The packages currently in debian stable was changed to use the "service" command, which should work with all init systems in Debian/Ubuntu at this time. The upstream changes look possible to backport to puppet 3.7. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1457957] Re: puppet uses upstart for service status checks in vivid
On Tue, May 26, 2015 at 03:16:04PM -, Ben Shephard wrote: > ...I think the issue stems from the upgrade not changing the > provider for service management from upstart to systemd I thought the providers are dynamically determined by puppet at runtime and not stored persistently anywhere? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
I've just tested this on a fresh build of 15.04 and it seems to work just fine so I think the issue stems from the upgrade not changing the provider for service management from upstart to systemd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
> Instead, one has to pay attention to which init system is active (I'm not sure what the "official" way is to do that, but we can find that out). Right. Checking files is *never* correct, as both in upstart and in systemd you can always override them (e. g. /etc/init/*.override or a file in /etc/systemd/system/ or /run/systemd/system/ overrides a file in /lib/systemd/system). > Or perhaps puppet should exclusively be using the "service" wrapper now That is the correct thing to do. service works under SysV, upstart, and systemd. The only thing to keep in mind is that "service status foo" always exits with 0 under upstart even if a service isn't running. Arguably this really ought to be fixed, so if you need that functionality let's fix that properly instead of working around it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
** Changed in: puppet (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Or perhaps puppet should exclusively be using the "service" wrapper now (/usr/sbin/service), certainly on Ubuntu and presumably on Debian? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Thank you for taking the time to report this bug and helping to make Ubuntu better. This sounds like an upstream puppet "bug" because Ubuntu follows the Debian design in the new world order. In Debian one might switch init systems at will, so the existence of service files in /etc/init/ or /etc/init.d/ or /{etc,lib}/systemd/system/ cannot really determine anything. Instead, one has to pay attention to which init system is active (I'm not sure what the "official" way is to do that, but we can find that out). Have upstream tackled this yet at all? If not, then I think it would be appropriate to file a bug there. Once upstream have settled on a fix, we can cherry-pick it to Vivid. ** Tags added: needs-upstream-report systemd-boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: puppet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs