** 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
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:
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
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
** 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
# 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
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.
@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
> 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
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.
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?
** 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
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
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
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
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.
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
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
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
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
** 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)
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
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
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
** 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
** 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
26 matches
Mail list logo
