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 thi
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
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 notification
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
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
** 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 bu
** 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 rep
** 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
** 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
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://bug
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
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 anywh
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 subscr
> 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/
** 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
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
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/in
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/1457
18 matches
Mail list logo
