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

Each release is getting a slightly different fix, unfortunately.

Zesty (4.8.2-3ubuntu1) is getting an adaptation of the Debian change
which simply makes systemd the default on all Ubuntu and then switches
back to upstart if it doesn't see /run/systemd/system (I will coordinate
with the Debian maintainers to see if this is going upstream).

Yakkety has a version of my upstreamed change, so we just add 16.10 to
the list.

Xenial is a much older codebase, but the minimal fix tested by a few
folks via my PPA still applies and is what I have uploaded. It resembles
the Debian and upstream fixes and is minimally invasive.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

** Description changed:

+ [Impact]
+ 
+  * Puppet incorrectly detects the service manager on Ubuntu 16.04 and
+ 16.10 as upstart, rather than systemd.
+ 
+  * Various puppet-driven commands fail as they do not use the systemd
+ interfaces.
+ 
+ [Test Case]
+ 
+  * # upstart is required to confuse Puppet
+ apt install -y puppet upstart tftpd-hpa
+ 
+ # fails without fix
+ puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
+ 
+ # install fixed package
+ 
+ # works
+ puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
+ 
+ [Regression Potential]
+ 
+  * Currently, puppet is unable to apply configurations to 16.04, 16.10
+ and 17.04 (fix is in -proposed for 17.04) when upstart is installed.
+ This change will make puppet correctly use systemd for service
+ manipulation, and I believe the likelihood of regression is low.
+ 
+  * The primary source of regressions would be users who have modified
+ their puppet installations to work around this issue. I believe they
+ will be generally unaffected by fixing the underlying issue.
+ 
+ ---
+ 
  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.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

** Changed in: puppet (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: puppet (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: puppet (Ubuntu Yakkety)
   Status: Confirmed => In Progress

** Changed in: puppet (Ubuntu Xenial)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: puppet (Ubuntu Yakkety)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

Debian has integrated some changes in this area, so I'm refreshing my
changes for Zesty, so I can pursue the SRU.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

** Also affects: puppet (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: puppet (Ubuntu Yakkety)
   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/1570472

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2017-02-15 Thread Saverio Proto

I tested the PPA from Nish Aravamudan
https://launchpad.net/~nacc/+archive/ubuntu/lp1570472

It fixes the problem for me. Any chance to have this merged to the
official packages ?

Saverio

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2017-01-11 Thread Walter Hop

For those who are running into this problem and stumble upon this bug:
adding the following to your "site.pp" file is a workaround. It sets
'systemd' as default provider for any service resource.

if $operatingsystem == 'Ubuntu' and versioncmp($operatingsystemrelease, 
'16.04') >= 0 {
# Sets the new systemd as default service provider on Ubuntu 16.04 and 
higher.
# Works around upstart being used by Puppet.
# See also: 
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472
Service {
provider => systemd
}
}

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-11-22 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: puppet (Ubuntu Xenial)
   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/1570472

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-11-21 Thread Nish Aravamudan

** Also affects: puppet (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-11-02 Thread ghomem

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.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-11-02 Thread ghomem

As the previous commenter said, upstart is still installed on default
Xenial desktops (with Unity). And those system need to be managed via
puppet as well. If you remove upstart the whole desktop breaks.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-10-24 Thread Neil Hoggarth

Upstart is still installed on desktop Xenial systems, even on a fresh
installation; the unity-greeter package depends on it. Attempting to
"apt-get remove upstart" also offers to remove the "ubuntu-desktop",
"unity", and "unity-greeter" packages, along with the "upstart" package.

So this bug prevents the use of Puppet from correctly managing any
services on a Xenial desktop system.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-08-25 Thread Nish Aravamudan

Apologies for the churn, but the above versions didn't pass GH's auto-
checks. Uploaded

4.5.2-1ubuntu2~ppa7
3.8.5-2ubuntu1~ppa8

which should match the current GH tree.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-08-25 Thread Nish Aravamudan

I apologize, I had a syntax error on my GH commit and thus the
backports. Fixed in GH just now (135ecbbcc98d) and uploaded to the PPA:

  4.5.2-1ubuntu2~ppa6 for 16.10
  3.8.5-2ubuntu1~ppa7 for 16.04

Thanks to Martin Stofko for pointing the issue out to me.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-08-24 Thread Nish Aravamudan

@Dmitry, I've pushed your changes to my tree on GH
(https://github.com/puppetlabs/puppet/pull/5133). Thanks!

I reworded it slightly to match what I think makes more sense
(running_on_systemd, rather than runs_on_systemd).

I'll submit some new testbuilds to the same PPA with the updates.

Should be:

4.5.2-1ubuntu2~ppa5 for 16.10
3.8.5-2ubuntu1~ppa6 for 16.04 (which should actually be 
3.8.5-2ubuntu0.1~ppa6, sorry!)

-Nish

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-08-22 Thread Nish Aravamudan

@Dmitry, thanks for the update! I'll test some other cases and see if we
can get it fixed up both upstream and in 16.04!

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-26 Thread Dmitry Teselkin

@nacc, I've tested puppet 3.8 from your ppa, and found one issue with it. It
looks like 'defaultfor' works well only when it compares values for facts.
:exists doesn't look like a fact, and defaultfor works incorrectly. I fixed it
by adding fact :runs_on_systemd and testing its value instead, see attached
patch.

Don't know if it applicable for puppet 4.5 though.

Without the patch

# puppet apply -dv --execute 'service{cron:}'
...
Info: Applying configuration version '1469565569'
Debug: Executing '/usr/sbin/service cron status'
Debug: Finishing transaction 30515820
Debug: Storing state
Debug: Stored state in 0.51 seconds
Notice: Finished catalog run in 1.09 seconds
...

With patch applied

# puppet apply -dv --execute 'service{cron:}'
...
Info: Applying configuration version '1469565628'
Debug: Executing '/bin/systemctl is-active cron'
Debug: Finishing transaction 33627360
Debug: Storing state
Debug: Stored state in 0.45 seconds
Notice: Finished catalog run in 1.11 seconds
...

I use Ubuntu 16.04.1, no upstart installed.

** Patch added: "runs_on_systemd.patch"

https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4707718/+files/runs_on_systemd.patch

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

Title:
Set systemd as default service provider

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

Updated the patches to match the version upstream that passes CI.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

I'm also working on changing upstream so this is not a delta in the
future with: https://github.com/puppetlabs/puppet/pull/5133

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

# apt-cache policy puppet
puppet:
  Installed: 3.8.5-2
  Candidate: 3.8.5-2
  Version table:
 *** 3.8.5-2 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy upstart
upstart:
  Installed: 1.13.2-0ubuntu21.1
  Candidate: 1.13.2-0ubuntu21.1
  Version table:
 *** 1.13.2-0ubuntu21.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.13.2-0ubuntu21 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
root@ubuntu:~# puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
Notice: Compiled catalog for untransubstantiated-vallie.lxd in environment 
production in 0.13 seconds
Error: /Stage[main]/Main/Service[tftpd-hpa]: Could not evaluate: Execution of 
'/sbin/status tftpd-hpa' returned 1: status: Unable to connect to Upstart: 
Failed to connect to socket /com/ubuntu/upstart: Connection refused
Notice: Finished catalog run in 0.02 seconds
...
[ ignore the bad version string this matches the debdiff just attached]
# apt-cache policy puppet
puppet:
  Installed: 3.8.5-2ubuntu1~ppa5
  Candidate: 3.8.5-2ubuntu1~ppa5
  Version table:
 *** 3.8.5-2ubuntu1~ppa5 500
500 http://ppa.launchpad.net/nacc/lp1570472/ubuntu xenial/main amd64 
Packages
100 /var/lib/dpkg/status
 3.8.5-2 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
# puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
Notice: Compiled catalog for untransubstantiated-vallie.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

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

# apt-cache policy puppet
puppet:
  Installed: 4.5.2-1ubuntu1
  Candidate: 4.5.2-1ubuntu1
  Version table:
 *** 4.5.2-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy upstart
upstart:
  Installed: 1.13.2-0ubuntu26
  Candidate: 1.13.2-0ubuntu26
  Version table:
 *** 1.13.2-0ubuntu26 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status
# puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
Notice: Compiled catalog for unputrefied-marleigh.lxd in environment production 
in 0.22 seconds
Error: /Stage[main]/Main/Service[tftpd-hpa]: Could not evaluate: Execution of 
'/sbin/status tftpd-hpa' returned 1: status: Unable to connect to Upstart: 
Failed to connect to socket /com/ubuntu/upstart: Connection refused
Notice: Applied catalog in 0.03 seconds
...
# apt-cache policy puppet
puppet:
  Installed: 4.5.2-1ubuntu2~ppa3
  Candidate: 4.5.2-1ubuntu2~ppa3
  Version table:
 *** 4.5.2-1ubuntu2~ppa3 500
500 http://ppa.launchpad.net/nacc/lp1570472/ubuntu yakkety/main amd64 
Packages
100 /var/lib/dpkg/status
 4.5.2-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages
# puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
Notice: Compiled catalog for unputrefied-marleigh.lxd in environment production 
in 0.23 seconds
Notice: /Stage[main]/Main/Service[tftpd-hpa]/ensure: ensure changed 'running' 
to 'stopped'
Notice: Applied catalog in 0.10 seconds

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

** Attachment removed: "attachment"
   
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4704984/+files/attachment

** Attachment removed: "attachment"
   
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4704985/+files/attachment

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-21 Thread Nish Aravamudan

To clarify one statement. The workaround only works because the base
'service' provider works regardless of upstart or systemd for tftpd-hpa.
Not sure it works generally. So we do want to fix this properly so
systemd is leveraged where it is running.

-Nish

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-21 Thread Nish Aravamudan

Alright, so this is a bug, but there is at least one clear workaround if you're 
on 15.04 or later, remove the 'upstart' package.
However, that's ugly, and I think there is a better fix, as in the attached 
debdiffs.

Please test https://launchpad.net/~nacc/+archive/ubuntu/lp1570472

Basically, my "fix" is to modify the provider logic in puppet so that
systemd is used (regardless of ubuntu's version) if systemd is running
(which is the case if /run/systemd/system exists, AIUI).

For 16.10, that is a small change to just remove the version checks for
the systemd provider.

For 16.04, that is a larger change to add the confine for
/run/systemd/system detection (similar to what is in 16.10, but without
the conditional, since this is an Ubuntu package) and add the ubuntu
default in the systemd provider.

In my testing, this fixes the issue in 16.04 and 16.10, with or without
upstart installed.

I've filed https://tickets.puppetlabs.com/browse/PUP-6531 so hopefully
upstream can remove the version checking logic, but in the meanwhile, we
should probably simply carry this change in puppet in Ubuntu as a delta.

-Nish

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-21 Thread Ivan Suzdal

@Nish, after a superficial RCA I can say here is probably some mistake from my 
side. Perhaps, in previous release (sadly I can't find particular ISO where I 
faced with issue) were some parts of upstart ('/sbin/start' for example) which 
causes issue like in comment #8.
For now I can't reproduce on a clean installation from latest available iso 
without explicit upstart installation.
So, you must be right about "a 14.04 -> 16.04 issue".

> what is the basis (test case) for the OP statement
Seems like you need to install upstart first.
I didn't make check on a latest ISO's, sorry for that.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-20 Thread Nish Aravamudan

On 20.07.2016 [11:13:13 -], Ivan Suzdal wrote:
> @Nish, from my point of view it's absolutely expected behavior. In this
> request, we trying to change default puppet service provider from
> 'upstart' to 'systemd'. So when you change your init system from
> 'systemd' to 'upstart' - puppet shall fall. Probably we can add another
> init system checks, but it's looks like overcomplicating of existing
> code.

Yes, I understand that. But "change default puppet service provider from
'upstart' to 'systemd'" is what I'm referring to -- where do you see
this? I need an explicit test-case so I can figure out where things are
wrong (esp. in the development release) and why.

As I mentioned in my last comment, *if* the upstart package was not
installed to begin with, I see no issues with puppet in 16.04. Was
this a 14.04 -> 16.04 issue?

More clearly, what is the basis (test case) for the OP statement of
"puppet thinks it's still upstart"?

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-20 Thread Robie Basak

On Wed, Jul 20, 2016 at 11:13:13AM -, Ivan Suzdal wrote:
> I guess 'upstart' shouldn't be installed by default in 16.04. But I'm
> not familiar enough with "replacing init system" policies in Ubuntu.
> It'll be fine if someone else can confirm.

Right now, I don't think the Ubuntu Server Team expects to support
anything other than systemd in releases since 15.04. If you think we
should, please take it up on the mailing list.

But since Debian supports multiple init systems and we inherit that
capability, I have no objection to patches to fix behaviour in the
development release, provided that we also have someone step up to
maintain any Ubuntu delta for this as required.

For fixing server and upstart related bugs in stable releases that ship
with systemd, I guess it probably depends on the individual regression
risk.

I originally thought that this bug affected puppet when running under
systemd as is the default. If this is not the case and only affects
upstart in a pretty unusual and unsupported (by the server team) system
configuration, then though I still welcome patches from users affected,
I would expect the Ubuntu Server Team to focus on other bugs instead.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-20 Thread Ivan Suzdal

@Nish, from my point of view it's absolutely expected behavior. In this
request, we trying to change default puppet service provider from
'upstart' to 'systemd'. So when you change your init system from
'systemd' to 'upstart' - puppet shall fall. Probably we can add another
init system checks, but it's looks like overcomplicating of existing
code.

I guess 'upstart' shouldn't be installed by default in 16.04. But I'm
not familiar enough with "replacing init system" policies in Ubuntu.
It'll be fine if someone else can confirm.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-19 Thread 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570472

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-15 Thread Dmitry Burmistrov

Hello!
This patch/issue doesn't seem really complicated. Do you need some help maybe? 
I'm hoping proper code would appear in this SRU - proper default provider is 
"must have" point.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-07-06 Thread Nish Aravamudan

@Robie,

So upstream discussions around this are ongoing. I am working with the
puppet community on the "right" fix, which I will pursue into 16.10 via
upstream (or via a fresh merge with Debian, depending). Would you be
willing to sponsor the fixes here so we can make some progress on this
bug in the meanwhile?

-Nish

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-06-27 Thread Nish Aravamudan

On 27.06.2016 [13:12:17 -], Robie Basak wrote:
> +-  defaultfor :operatingsystem => :ubuntu, :operatingsystemmajrelease => 
> ["15.04","15.10","16.04"]
> ++  defaultfor :operatingsystem => :ubuntu, :operatingsystemmajrelease => 
> ["15.04","15.10","16.04","16.10"]
> 
> This will regress as soon as Yakkety+1 opens. Can we fix it properly?
> The logic should be "systemd for >= 15.04". That may need something
> better than a set of string comparisons. But doing anything different is
> clearly broken.

This logic is "easy" to modify for that, but the other iteration (also
a version list) is not, as it's not using a comparison, but extracting
the value itself.

I have asked upstream in https://github.com/puppetlabs/puppet/pull/5009
about this and your other suggestion.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-06-27 Thread Robie Basak

+-  defaultfor :operatingsystem => :ubuntu, :operatingsystemmajrelease => 
["15.04","15.10","16.04"]
++  defaultfor :operatingsystem => :ubuntu, :operatingsystemmajrelease => 
["15.04","15.10","16.04","16.10"]

This will regress as soon as Yakkety+1 opens. Can we fix it properly?
The logic should be "systemd for >= 15.04". That may need something
better than a set of string comparisons. But doing anything different is
clearly broken.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-06-27 Thread Robie Basak

Or, if you like, reverse it: systemd by default, upstart only for the
known set of releases that shipped with upstart. Presumably pre-upstart
is before any currently supported release, so we don't need to worry
about that.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-06-21 Thread Mathew Hodson

** Changed in: puppet (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2016-06-14 Thread Simon Déziel

@Nish, I used the simple test case from comment #20 on Yakkety:

3.8.5-2: fails
4.5.0-4: fails
4.5.0-4ubuntu1: works

As for the autopkgtest failures, I don't know what's going on either as
it works for me too in a LXD container.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

@Simon, actually the above build build only fixes the test failure for
puppet-module-asciiduck-sssd, the puppet-module-puppetlabs-ntp failure
still occurs. However, I noticed that if I drop to a shell in a local
LXD based test-run, the run-tests script passes. Do you have any idea
what might be going on? I don't know enough about puppet to know how to
fix that. It also seems to be an issue with Debian's autopkgtests.

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

This latest debdiff has been tested (by me) to fix the testsuite
regressions in yakkety-proposed with 4.5.0-4.

I have just uploaded the same to:
https://launchpad.net/~nacc/+archive/ubuntu/lp1570472.

@Simon, once the above is finished building, if you could test it in
Yakkety, then Robie should be able to sponsor, and we work on the SRU. I
will prepare the appropriate debdiff to test for 16.04 shortly.

Thanks!
-Nish

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

** Changed in: puppet (Ubuntu)
 Assignee: Simon Déziel (sdeziel) => Nish Aravamudan (nacc)

** Attachment added: "attachment"
   https://bugs.launchpad.net/bugs/1570472/+attachment/4683960/+files/attachment

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

Title:
  Set systemd as default service provider

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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