*** This bug is a duplicate of bug 1570472 ***
https://bugs.launchpad.net/bugs/1570472
** This bug has been marked a duplicate of bug 1570472
Set systemd as default service provider
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can also confirm that PPA @gustavo linked to works for that puppet +
ubuntu version.
Thanks for the fix. Ok now back to puppet'ing.
L
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
I confirm that
puppet-3.8.5-2
from this PPA
https://launchpad.net/~nacc/+archive/ubuntu/lp1570472
resolves the problem, at least on Ubuntu 16.04 x64.
This was suggested on Bug #1570472. Thanks Mathew Hodson for pointing
out.
--
You received this bug notification because you are a member of
@mathey hodson
yes ,this bug is the same as Bug #1570472.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
puppet uses upstart for service status checks in vivid
To manage
Is this the same as Bug #1570472 ?
That bug has a patch that will make systemd the default if it is
running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
puppet uses upstart for
This affects 16.04 desktop.
I'm using a KDE based version, without unity, etc and I managed to
remove upstart without dependency problems - simply ran "apt-get remove
upstart".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial is affected by that as well -> standard setup and puppet service
calls fail
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
puppet uses upstart for service status checks in
Christian, how did you manage to uninstall upstart package without breaking the
whole system?
On my updated systems, when I try to uninstall upstart, apt-get says it have to
remove ubuntu-desktop, unity and unity-greeter:
root@:~# LANG=C apt-get purge upstart
Reading package lists... Done
Recent merges have "somewhat" fixed this issue, but only if upstart is not
installed.
And @Robie - yes it was related to bug 1495853
Tested in Wily containers with:
apt-get install openssh-server
apt-get install puppet
puppet resource --debug --param provider --param enable service ssh
puppet
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
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
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
Experiencing this on 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
I also ran into that problem on 15.10 beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
puppet uses upstart for service status checks in vivid
To manage notifications about this
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
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.
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
Bugs, which is subscribed to Ubuntu.
Is this related to bug 1495853?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
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
** 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
** 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
Bugs, which is subscribed to Ubuntu.
** 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
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
** 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
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
** 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
** 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.
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
Bugs, which is subscribed to Ubuntu.
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
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.
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
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
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
** 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
** Changed in: puppet (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
puppet uses upstart for service status checks in vivid
To manage
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457957
Title:
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
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
Bugs, which is subscribed
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
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
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
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
45 matches
Mail list logo
