@askb23: There is no Ubuntu-provided puppet 4.9.4 (not even on 17.04).
Please contact upstream puppet for support.
** Changed in: puppet (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: puppet (Ubuntu Xenial)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** C
I am hitting the same issue even with latest version of puppet4 of 4.9.4
on ubuntu 16.04:
cat file.pp
--
if $operatingsystem == 'Ubuntu' and versioncmp($operatingsystemrelease,
'16.04') >= 0 {
# Sets the new systemd as default service provider on Ubuntu 16.04 and higher.
This bug was fixed in the package puppet - 4.5.2-1ubuntu1.1
---
puppet (4.5.2-1ubuntu1.1) yakkety; urgency=medium
* debian/patches/0004-update_systemd_default_16.10.patch: Indicate
systemd is also the default on 16.10. Closes LP: #1570472.
-- Nishanth Aravamudan Fri, 17 Feb
This bug was fixed in the package puppet - 3.8.5-2ubuntu0.1
---
puppet (3.8.5-2ubuntu0.1) xenial; urgency=medium
* debian/patches/0008-Default-to-systemd-if-systemd.patch: systemd is
the default service provider if it is running. Closes LP: #1570472.
-- Nishanth Aravamudan
@nacc, hello. It's great news!
I've tested package from "-proposed" and can confirm it works. But as an
always, it would be nice if someone else could confirm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Changed in: puppet (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: puppet (Ubuntu Xenial)
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
This bug was fixed in the package puppet - 4.8.2-3ubuntu2
---
puppet (4.8.2-3ubuntu2) zesty; urgency=medium
* d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb: specify
to curl that 'puppet' should not be proxied.
* d/t/control: generate a certificate for puppet maste
Tested on both xenial and yakkety with the provided testcase. Without
-proposed, the testcase fails with:
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
Hello Ivan, or anyone else affected,
Accepted puppet into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/puppet/4.5.2-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Changed in: puppet (Ubuntu Yakkety)
Status: Incomplete => In Progress
** Changed in: puppet (Ubuntu Xenial)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Unrelated to this fix. It's a networking issue with the tests that I'm
trying to resolve (https proxy in a sub-VM).
--
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 defaul
puppet 4.8.2-3ubuntu1 is stuck in zesty-proposed due to an autopkgtest
failure that appears to be related to systemd - so related to this fix?
Please check.
** Changed in: puppet (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: puppet (Ubuntu Yakkety)
Status: In Prog
Hi zioproto,
documenting here as just discussed on LP.
Step 5 of https://wiki.ubuntu.com/StableReleaseUpdates#Procedure is what
applies here.
That means Nish has uploaded it and you can see it (at the moment) in e.g.:
https://launchpad.net/ubuntu/yakkety/+queue?queue_state=1
https://launchpad.net
Hello Nish,
what is the workflow for Xenial ? are we going to see new puppet packages in
Xenial Proposed repo soon ?
thank you
--
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 syste
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 main
** 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
** 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
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
** 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/bug
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
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 {
# Set
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
** 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 no
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/1
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 subsc
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 preve
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.laun
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
@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 b
@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 d
@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
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
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 syste
# 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:
# 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-0u
** 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
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 b
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
@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 o
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
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 e
@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
@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 pu
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.
htt
@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
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
+- 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 b
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
B
** 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
@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 U
@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 goi
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 b
** 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 i
** Changed in: puppet (Ubuntu)
Assignee: Nish Aravamudan (nacc) => Simon Déziel (sdeziel)
--
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
T
Just an FYI to document what Simon and I discussed on IRC. We did an
upstream fix (https://github.com/puppetlabs/puppet/pull/5009) which has
been merged to use systemd on 16.10. We can then backport that to the
Ubuntu package (Simon is planning on this), which will fix Yakkety. We
then can properly
** Changed in: puppet (Ubuntu)
Status: Fix Committed => In Progress
--
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 notificatio
When I fool puppet into thinking that Yakkety is version 16.04, it
works. Here's what I did in a Yakkety container:
# upstart is required to confuse Puppet
apt-get install -y puppet upstart tftpd-hpa # note: puppet-common is gone
# fails
puppet apply -e "service { 'tftpd-hpa': ensure => stopped }
@nacc, the proposed version in Yakkety (4.5.0-4) is also affected. This
probably makes sense because upstream only enables systemd handling
based on known and hardcoded version numbers. Since 16.10 is not one of
those, upstart is implied by default.
--
You received this bug notification because y
@Simon, I think the new debdiff is an improvement, but I have the
following questions/requests:
1) Can you add more DEP3 headers? Author and Source are missing, I think. I
think this is especially important since we're folding multiple upstream
commits into one.
2) Can you use dep3changelog to m
@Simon and others affected, I noticed that puppet in Yakkety is at
4.5.0-4 in proposed. Can that be tested as well, that way we can confirm
the fix is already released in the development release and then work on
the SRU/backport.
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Committ
Same debdiff but with a proper address in the changelog.
** Patch removed: "lp1570472-version-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4675541/+files/lp1570472-version-2.debdiff
** Patch added: "lp1570472-version-2.debdiff"
https://bugs.launchpa
@nacc, I aggregated all the commits you mentioned in update 5. I needed
to apply some parts manually, especially for the spec/ tests portions.
# upstart is required to confuse Puppet
apt-get install -y puppet-common upstart tftpd-hpa
# fails
puppet apply -e "service { 'tftpd-hpa': ensure => stop
@Dmitry, sorry I have been busy with a few other tasks, I will look at
this today or tomorrow and respond.
--
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
@Simon, would you be able to help me determine if the other upstream
patches are necessary or not? I worry that while it may work for some
testers in some environments, that unless we backport the complete set
of upstream-related changes, there will be some broken situations still.
--
You receive
Is this patch confirmed? Is it going to be included 16.04.1 update?
--
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 abou
Simon, thank you for the debdiff. Sorry we didn't manage to get to this
in the week before release. I think this probably does qualify for an
SRU.
Nish, would you mind driving this please? I'll be happy to sponsor
following your review. We need to make sure this is fixed in the
development release
Hi, please add this patch to next release.
--
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:/
@Nish, is any ETA here? Could I help somehow yet?
--
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:
I've tested the diff in #4 on Ubuntu 16.04, with puppet-common 3.8.5-2,
it seems to fix the issue correctly.
Prior to the patch, Puppet would try and manage services using upstart:
/Stage[main]/Tftp::Service/Service[tftpd-hpa]: Could not evaluate:
Execution of '/sbin/status tftpd-hpa' returned 1:
I've tested simple manifest which includes 'ensure service running' on
15.04 and 15.10 and have no faced with any issues.
--
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
In my case these changes were enough. Not sure what other changes
weren't necessary - I checked on the 16.04 and unfortunately I've no
opportunity to check on an early releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@Simon, @Ivan, looking upstream, this seems to be a combination of:
https://github.com/puppetlabs/puppet/commit/7fe61647f23650fc4c93cd6b54c654a20ff7c9f9
https://github.com/puppetlabs/puppet/commit/920d58df681bf02e5293686c704d89d71baa0f28
https://github.com/puppetlabs/puppet/commit/9000a5da80487429
I am also interested in this so here's a debdiff.
** Patch added: "lp1570472.debdiff"
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4637132/+files/lp1570472.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Ivan, have you ever produced a debdiff before? Would you be comfortable
updating your diff to be a proper debdiff against the current puppet
package?
** Changed in: puppet (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The attachment "patch for puppet (v3.8.5-2)" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~
75 matches
Mail list logo
