[Bug 1570472] Re: Set systemd as default service provider

[Nish Aravamudan]

@Ivan, @Simon, @Dmitry, or anyone else affected:

I'm trying to understand exactly what is wrong/expected here (not overly
familiar with puppet myself).

So Simon's test case was `puppet apply -e "service { 'tftpd-hpa': ensure
=> stopped }"`.

On 16.04 and 16.10, without 'upstart' installed (but puppet and tftpd-
hpa), I get:

puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
Notice: Compiled catalog for nonfermentable-maribeth.lxd in environment production in 0.14 seconds
Notice: /Stage[main]/Main/Service[tftpd-hpa]/ensure: ensure changed 'running' to 'stopped'
Notice: Finished catalog run in 0.19 seconds

and `service tftpd-hpa status` indicates it is properly stopped.

If I install the 'upstart' package, things break, but that shouldn't be
installed by default in 16.04 anymore?

What am I missing? What command reproduces the exact issue you are
seeing Ivan?

FWIW, the 16.10 version of puppet has the versioned code already present
(although not the bit for 16.10). But again, in 16.10 the same behavior
is seen. So I think I need a clearer statement of the problem so I can
verify the fix better.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1570472

Title:
  Set systemd as default service provider

Status in puppet package in Ubuntu:
  In Progress

Bug description:
  AFAIK, Ubuntu has systemd as default init system since 15.04 release. Although, puppet thinks it's still upstart.
  This behavior is already fixed in upstream puppet code. Please, add this patch to Xenial puppet package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+subscriptions