[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Dan Streetman]

** Changed in: systemd (Ubuntu Trusty)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Launchpad Bug Tracker]

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

** Changed in: systemd (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/1732703

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Launchpad Bug Tracker]

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

** Changed in: systemd (Ubuntu Trusty)
   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/1732703

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Launchpad Bug Tracker]

This bug was fixed in the package maas - 1.9.5+bzr4599-0ubuntu1~14.04.3

---
maas (1.9.5+bzr4599-0ubuntu1~14.04.3) trusty-proposed; urgency=medium

  * Stable Release Update.
- debian/patches/harcode-upstart-lp1732703.patch: Running snapd or
  livepatch in Trusty installs systemd. Due to a systemd regressions,
  this causes  MAAS to incorrectly detect the init system. As such,
  hardcode the init system to upstart (as systemd is not supported
  in Ubuntu) (LP: #1732703).

 -- Andres Rodriguez   Wed, 13 Dec 2017 18:09:11
-0500

** Changed in: maas (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Victor Tapia]

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Ivan Hitos]

# VERIFICATION FOR TRUSTY

- Packages
---
# dpkg -l|grep maas
ii  maas   1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS server all-in-one metapackage
ii  maas-cli   1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS command line API tool
ii  maas-cluster-controller1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS server cluster controller
ii  maas-common1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS server common files
ii  maas-dhcp  1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS DHCP server
ii  maas-dns   1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS DNS server
ii  maas-proxy 1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS Caching Proxy
ii  maas-region-controller 1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS server complete region controller
ii  maas-region-controller-min 1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS Server minimum region controller
ii  python-django-maas 1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS server Django web framework
ii  python-maas-client 1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS python API client
ii  python-maas-provisioningserver 1.9.5+bzr4599-0ubuntu1~14.04.3   all 
 MAAS server provisioning libraries
 
 
- Tests
---
Update maas from proposed. Add to /etc/apt/sources.list:
deb [arch=amd64] http://archive.ubuntu.com/ubuntu trusty-proposed multiverse 
restricted main universe
deb-src [arch=amd64] http://archive.ubuntu.com/ubuntu trusty-proposed 
multiverse restricted main universe

- DNS+DHCP do work as expected (monitor does not ask systemd)
- Try enlisting -> works
- Try commissioning -> works
- Try deployment -> works
- Try deleting -> works
- Verified that both upgrade and install works:
# apt update + upgrade
# apt install maas

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Brian Murray]

Hello Victor, or anyone else affected,

Accepted maas into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/maas/1.9.5+bzr4599-0ubuntu1~14.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: maas (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-trusty

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Andres Rodriguez]

@I've uploaded the new package. I've tested an upgrade to Xenial to
ensure there are no issues and confirm it is good to go.

** Changed in: maas/1.9
 Assignee: Andres Rodriguez (andreserl) => (unassigned)

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

> I would accept a version of this SRU that hard-codes the choice of
upstart as the init system on 14.04, because that is the only init
system supported in that version of Ubuntu.

OK, that sounds like a reasonable way forward. I've rejected the current
upload in the queue, and I believe Andres has agreed to upload a revised
version shortly.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

We concluded that this isn't a snapd bug, except in so far as it depends
on systemd.

** Changed in: snapd (Ubuntu Trusty)
   Status: New => Invalid

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

Re: [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Andres Rodriguez]

On Wed, Dec 13, 2017 at 6:00 PM Robie Basak <1732...@bugs.launchpad.net>
wrote:

> On Wed, Dec 13, 2017 at 10:34:25PM -, Andres Rodriguez wrote:
> > FWIW, this is currently affecting customers who are running MAAS and
> > require livepatch.
>
> It's been affecting users since January, no?


This hasn’t been affecting users since January. This bug has been reported
in November and only affects users running MAAS who someway or another
installed systemd. In this particular case, on November a customer
installed live patch on a system, hence the issue.

Why the sudden urgency?
> What difference will a week or two make?
>
> > Comments #11 and #12 above confirm that the patch is enough for the MAAS
> > needs. Whichever way MAAS decides to check for systemd is up to MAAS and
> > that is not a reason to block an SRU provided that it does not impact
> > any other piece of software. That said, this patch does not does not
> > introduce  a regression to MAAS nor any other software.
>
> I think that's quite a brave claim to make. I'm sure "does not
> introduce a regression" was a claim that might have been made in the
> systemd SRU that regressed this too, and yet here we are.


There is no supported way on Ubuntu Trusty (nor package in the archive)
that will create a symlink of /sbin/init to systemd. This only happens By
the systemd-sysv package which is only available in Xenial. So, since
systemd is not supported as a init system in trusty and this would only
happen if a user manually does this, then this doesn’t introduce any
regressions in MAAS. So it is not a brave claim to make, it is a claim
based on facts.

>
>
> > Lastly, this patch is *only* for 1.9 as this code path is only available
> > in Trusty, so upgrades to later Ubuntu releases will yield on using a
> > newer version of MAAS that doesn't rely on this code path.
>
> If we did decide to SRU an emergency fix as a stopgap for MAAS' use
> case, and it's for Trusty only, then why have a test at all? Can we just
> return 'upstart' without a test?
>
> To be clear, I'm not demanding or even requesting anything specific
> right now. I don't feel that a case for urgency has yet been made, given
> the currently known regression timeline. In the meantime I think it's
> worth understanding how we want to fix this properly, because requiring
> multiple SRUs while we swing back and forth is bad for everyone, and
> equally I don't want to see us locked into a suboptimal solution.
>
> If a case is accepted on the basis of urgency, or another SRU team
> member disagrees with my assessment, I wouldn't want to block that. Feel
> free to land what you think is appropriate.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1732703
>
> Title:
>   MAAS does not detect properly if Ubuntu is using upstart/systemd
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; status=Won't Fix; importance=Undecided;
> assignee=None;
> Launchpad-Bug: product=maas; productseries=1.9; milestone=1.9.6; status=In
> Progress; importance=Critical; assignee=andres...@ubuntu-pe.org;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=maas; component=main;
> status=New; importance=Critical; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=snapd; component=main;
> status=Won't Fix; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=systemd; component=main;
> status=New; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=trusty;
> sourcepackage=maas; component=main; status=New; importance=Undecided;
> assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=trusty;
> sourcepackage=snapd; component=universe; status=New; importance=Undecided;
> assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=trusty;
> sourcepackage=systemd; component=main; status=New; importance=Critical;
> assignee=None;
> Launchpad-Bug-Tags: regression-update sts
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: afreiberger andreserl racb vorlon vtapia xnox
> Launchpad-Bug-Reporter: Victor Tapia (vtapia)
> Launchpad-Bug-Modifier: Robie Basak (racb)
> Launchpad-Message-Rationale: Assignee
> Launchpad-Message-For: andreserl
>
-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[David Britton]

** Changed in: maas (Ubuntu)
   Status: New => Won't Fix

** Changed in: maas (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: maas (Ubuntu Trusty)
   Importance: Undecided => Critical

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Steve Langasek]

I would accept a version of this SRU that hard-codes the choice of
upstart as the init system on 14.04, because that is the only init
system supported in that version of Ubuntu.

We can discuss further whether the deput-init systemd package in trusty
needs further changes to not fall afoul of common init system detection
techniques, but I don't think that should block fixing MAAS in this
scenario.

Currently, all the proposed methods of detecting the init system have
corner cases where they break.  Most of these corner cases are
negligible for maas, however.

The one option I know that doesn't have corner cases is to invoke
'/sbin/initctl version' and check its return code.  But I leave it up to
the MAAS team whether to implement this vs. a lighter-weight check.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

Re: [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

On Wed, Dec 13, 2017 at 10:34:25PM -, Andres Rodriguez wrote:
> FWIW, this is currently affecting customers who are running MAAS and
> require livepatch.

It's been affecting users since January, no? Why the sudden urgency?
What difference will a week or two make?

> Comments #11 and #12 above confirm that the patch is enough for the MAAS
> needs. Whichever way MAAS decides to check for systemd is up to MAAS and
> that is not a reason to block an SRU provided that it does not impact
> any other piece of software. That said, this patch does not does not
> introduce  a regression to MAAS nor any other software.

I think that's quite a brave claim to make. I'm sure "does not
introduce a regression" was a claim that might have been made in the
systemd SRU that regressed this too, and yet here we are.

> Lastly, this patch is *only* for 1.9 as this code path is only available
> in Trusty, so upgrades to later Ubuntu releases will yield on using a
> newer version of MAAS that doesn't rely on this code path.

If we did decide to SRU an emergency fix as a stopgap for MAAS' use
case, and it's for Trusty only, then why have a test at all? Can we just
return 'upstart' without a test?

To be clear, I'm not demanding or even requesting anything specific
right now. I don't feel that a case for urgency has yet been made, given
the currently known regression timeline. In the meantime I think it's
worth understanding how we want to fix this properly, because requiring
multiple SRUs while we swing back and forth is bad for everyone, and
equally I don't want to see us locked into a suboptimal solution.

If a case is accepted on the basis of urgency, or another SRU team
member disagrees with my assessment, I wouldn't want to block that. Feel
free to land what you think is appropriate.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Andres Rodriguez]

FWIW, this is currently affecting customers who are running MAAS and
require livepatch.

Comments #11 and #12 above confirm that the patch is enough for the MAAS
needs. Whichever way MAAS decides to check for systemd is up to MAAS and
that is not a reason to block an SRU provided that it does not impact
any other piece of software. That said, this patch does not does not
introduce  a regression to MAAS nor any other software.

Lastly, this patch is *only* for 1.9 as this code path is only available
in Trusty, so upgrades to later Ubuntu releases will yield on using a
newer version of MAAS that doesn't rely on this code path.

That said, there's no supported way in Ubuntu that will symlink
/sbin/init -> /lib/systemd/systemd , provided that systemd-sysv is
*only* available in Xenial, and again, upgrades to Xenial will result in
MAAS not using this codepath at all.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

I've deferred my decision as to whether to accept what's currently in
the queue on this thread: https://lists.ubuntu.com/archives/ubuntu-
devel/2017-December/040093.html

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Dimitri John Ledkov]

It is correct, in general, to check for /run/systemd/system to detect if
systemd manages pid 1.

Imho deputy systemd (used by snapd, on trusty, with xenial-lts kernel)
should not have been creating that, however I fear that without that
directory snapd and snaps therein may get confused (in classic
confinment).

It is true that trusty only uses upstart as pid1 with no other options;
and any system systemd jobs are inert (deputy systemd only looks for
deputy things).

Note that although xenial ships both upstart & systemd; only systemd is
supported as pid1 on all form-factors. (upstart as pid1 is only
supported on xenial ubuntu touch product, which is now end-of-life).

Possibly we could create one more directory e.g. /run/dsystemd/system or
some such, which maas can check for to destinguish "systemd or deputy-
systemd".

However, checking /sbin/init like done in the proposed merge proposal is
very adequate for maas needs, and should yield correct results. As far
as I can tell, since on xenial either upstart-sysv or systemd-sysv may
provide /sbin/init, with systemd-sysv being the default everywhere.
(upstart-sysv on xenial is for ubuntu touch only).

Ideally, I do not want to touch deputy systemd uploads.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Dimitri John Ledkov]

This is quite unique to maas; as no other software is getting backports
with explicit features that enables systemd support on trusty. E.g.
cloud-init backports are done in such a way, that when compiled on
trusty, no systemd support is installed nor available.

You may want to choose to make init-system selection code innert, as a
compile time / dependency option, such that on trusty there is no
dynamic selection of things at all.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

Further extensive discussion at https://irclogs.ubuntu.com/2017/12/13
/%23ubuntu-devel.html#t15:15

Our current belief is that the bug is in the systemd package, introduced
by the SRU tracked in bug 1656280. That update broke our standard test
for determining if we're on a systemd system by creating
/run/systemd/system when the systemd package is installed even if pid 1
is upstart.

It looks like this regressed eleven months ago but was only reported
last month, so I don't think the MAAS fix is critical. I would prefer to
get this fixed properly in systemd because it may have a wider impact
than just MAAS.

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Steve Langasek]

snapd will not function without systemd as a deputy init.  nothing to
fix in snapd.

** Changed in: snapd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: maas (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: snapd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Trusty)
   Importance: Undecided => Critical

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

15:15  roaksoax: in bug 1732703, I'm not sure that test for systemd is 
reliable. For example immediately after an upgrade from Trusty to Xenial, 
before a reboot, /sbin/init will be systemd but the running init system will be 
upstart.
15:15  bug 1732703 in MAAS 1.9 "MAAS does not detect properly if Ubuntu 
is using upstart/systemd" [Critical,In progress] 
https://launchpad.net/bugs/1732703
15:16  roaksoax: AFAICT, the "correct" way to test for systemd is its 
process name or something, but I can't find a good reference. 
15:16  roaksoax: so I'm not really sure what is correct. I'll happily 
accept whatever a systemd-type person here says. 
15:16  There should be something in one of the init script layers
15:17  /lib/lsb/init-functions.d/40-systemd
15:17  if [ -d /run/systemd/system ]; then
15:17  Ah
15:17  I believe that's the canonical method
15:17  I recalled something about something in /run but was unable to 
find it.
15:18  Thanks 
15:18  rbasak: Found the documentation for that - sd_booted(3)
15:19  under NOTES

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

Actually, if snapd isn't installed by default on Trusty, perhaps it we
shouldn't treat it as a regression caused by snapd as the user is
explicitly pulling in snapd and therefore systemd rather than it being
imposed automatically by the SRU. I'll leave it for others to decide
this though.

** Also affects: snapd (Ubuntu)
   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/1732703

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Robie Basak]

Since snapd pulling in systemd was introduced in an SRU, this is a
regression in a stable caused by an SRU and therefore should be
considered regression-update.

** Tags added: regression-update

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/334930

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

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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

[Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd

[Andres Rodriguez]

** Description changed:

- Trusty uses upstart by default, and installing snapd (e.g. for livepatch
- purposes), pulls systemd too. In this setup, upstart is _not_ replaced
- by systemd, but MAAS "detects" systemd as init because of the existence
- of /run/systemd/system:
+ [impact]
+ Since Trusty uses upstart by default, MAAS manages its services with upstart. 
However, when a user installs systemd (even if it is not used as the init 
system), MAAS detects systemd installed and tries to manage its services via 
systemd. This obviously creates issues and prevents MAAS from working.
+ 
+ [Test Case]
+ 1. Install & configure MAAS
+ 2. Add machines
+ 3. install systemd
+ 4. MAAS will fail to manage machines
+ 
+ [Regression potential]
+ Minimal. This just ensures that upstart is detected correctly even if systemd 
is installed (but not used).
+ 
+ [Original bug report]
+ Trusty uses upstart by default, and installing snapd (e.g. for livepatch 
purposes), pulls systemd too. In this setup, upstart is _not_ replaced by 
systemd, but MAAS "detects" systemd as init because of the existence of 
/run/systemd/system:
  
  @src/provisioningserver/utils/__init__.py:505
  
  SYSTEMD_RUN_PATH = '/run/systemd/system'
  
- 
  def get_init_system():
- """Returns 'upstart' or 'systemd'."""
- if os.path.exists(SYSTEMD_RUN_PATH):
- return 'systemd'
- else:
- return 'upstart'
+ """Returns 'upstart' or 'systemd'."""
+ if os.path.exists(SYSTEMD_RUN_PATH):
+ return 'systemd'
+ else:
+ return 'upstart'
  
  One possible solution would be to check if /sbin/init is a symlink
  pointing to /lib/systemd/systemd:
  
  def get_init_system():
- """Returns 'upstart' or 'systemd'.""" 
- initpath = os.readlink("/sbin/init") 
- if (initpath == "/lib/systemd/systemd"): 
- return 'systemd' 
- else: 
- return 'upstart' 
+ """Returns 'upstart' or 'systemd'."""
+ initpath = os.readlink("/sbin/init")
+ if (initpath == "/lib/systemd/systemd"):
+ return 'systemd'
+ else:
+ return 'upstart'
  
- 
- Other affected parts of the code are the postinst files for maas-proxy and 
maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an 
error if maas is installed after systemd in Trusty
+ Other affected parts of the code are the postinst files for maas-proxy
+ and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst),
+ throwing an error if maas is installed after systemd in Trusty

** Also affects: maas (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: maas (Ubuntu)
   Importance: Undecided => Critical

** Changed in: maas/1.9
   Status: Triaged => 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/1732703

Title:
  MAAS does not detect properly if Ubuntu is using upstart/systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions

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