[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
*** 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 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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: 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
@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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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 service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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 vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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 Building dependency tree Reading state information... Done The following packages will be REMOVED: ubuntu-desktop* unity* unity-greeter* upstart* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. 6 not fully installed or removed. After this operation, 9 203 kB disk space will be freed. Do you want to continue? [Y/n] David. -- 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457957] Re: puppet uses upstart for service status checks in vivid
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 resource --debug --param provider service ssh ensure=stopped
puppet resource --debug --param provider service ssh enable=false
puppet resource --debug --param provider service ssh enable=true
Just one snippet of these how things now work:
puppet resource --debug --param provider service ssh enable=true
Debug: Runtime environment: puppet_version=3.7.2, ruby_version=2.1.5,
run_mode=user, default_encoding=US-ASCII
Debug: Puppet::Type::Service::ProviderRedhat: file /sbin/chkconfig does not
exist
Debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not
exist
Debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist
Debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not
exist
Debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not
exist
Debug: Puppet::Type::Service::ProviderOpenrc: file /bin/rc-status does not exist
Debug: Puppet::Type::Service::ProviderUpstart: file /sbin/start does not exist
Debug: Loaded state in 0.00 seconds
Debug: Executing '/usr/sbin/service ssh status'
Debug: Executing '/bin/systemctl show -pSourcePath ssh'
Debug: Executing '/bin/systemctl is-enabled ssh'
Debug: Finishing transaction 27170800
Debug: Storing state
Debug: Stored state in 0.01 seconds
Debug: Executing '/usr/sbin/service ssh status'
Debug: Executing '/bin/systemctl show -pSourcePath ssh'
Debug: Executing '/bin/systemctl is-enabled ssh'
service { 'ssh':
ensure => 'running',
enable => 'true',
provider => 'debian',
}
As pitti suggested it uses the service wrapper now.
To be 100% sure that we have no issue with an 14.04->16.04 upgrade path leaving
stale files that might affect this I tested that as well.
One could nicely see that before the upgrade it was upstart
[...]
Debug: Executing '/sbin/status ssh'
[...]
provider => 'upstart',
$ do-release-upgrade -d
+ Same puppet commands again
There things got interesting.
While still having the new puppet version it is now running into mentioned
issues:
Debug: Executing '/sbin/status ssh'
Error: /Service[ssh]: Could not evaluate: Execution of '/sbin/status ssh'
returned 1: status: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
The difference seems to be the existance of /sbin/start in the system that got
upgraded 14.04 -> 16.04.
The clean 16.04 has:
Debug: Puppet::Type::Service::ProviderUpstart: file /sbin/start does not exist
But the upgraded system has upstart installed, and due to that runs into the
issues.
Just having it installed does not mean it IS the current init system.
Removing upstart on the 14.04->16.04 upgraded system resolves the situation.
It detects it as provider => debian then and works.
Vice versa if you install the upstart package on the clean 16.04 it runs into
the same issues.
So TL;DR
- puppets detection which provider to use seems to base on file checking
- newer puppet versions have fixes for systemd
- but upstart seems to have precedence - as soon as package upstart is
installed it switches from provider 'debian' to 'upstart'
Debug: Executing '/sbin/status ssh'
Error: /Service[ssh]: Could not evaluate: Execution of '/sbin/status ssh'
returned 1: status: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
- Root cause: /sbin/start being installed does not mean upstart is the one
being used
Simplified Testcase:
in Xenial container
$ apt-get install openssh-server
$ apt-get install puppet
Switch between good/bad case by installing/removing "upstart"
GOOD CASE - these are working
$ puppet resource --debug --param provider --param enable service ssh
$ puppet resource --debug --param provider service ssh enable=true
BAD CASE - these are failing
$ puppet resource --debug --param provider --param enable service ssh
[...]
Debug: Executing '/sbin/initctl list'
Error: Could not run: #
$ puppet resource --debug --param provider service ssh enable=true
[...]
Error: /Service[ssh]: Could not evaluate: Execution of '/sbin/status ssh'
returned 1: status: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
--
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:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
** 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
** 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. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
** 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
** 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
[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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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 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: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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
