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 <andres...@ubuntu.com> 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1732703
Title:
MAAS does not detect properly if Ubuntu is using upstart/systemd
Status in MAAS:
Won't Fix
Status in MAAS 1.9 series:
In Progress
Status in maas package in Ubuntu:
Won't Fix
Status in snapd package in Ubuntu:
Won't Fix
Status in systemd package in Ubuntu:
New
Status in maas source package in Trusty:
Fix Released
Status in snapd source package in Trusty:
Invalid
Status in systemd source package in Trusty:
New
Bug description:
[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'
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'
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
