I just filed bug 1623868 which is fallout from this change, so blocking
this SRU for now.
** Tags removed: verification-done
** Tags added: verification-failed
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
fully support package installation in systemd
Status in cloud-init:
Status in cloud-init package in Ubuntu:
Status in init-system-helpers package in Ubuntu:
Status in cloud-init source package in Xenial:
Status in init-system-helpers source package in Xenial:
in cloud-init users can install packages via cloud-config:
Due to some intricacies of systemd and service installation that doesn't work
all that well.
We fixed the issue for simple services that do not have any dependencies on
other services, or at least don't check those dependencies well under bug
We'd like to have a way to fully support this in cloud-init.
* bug 1575572: apache2 fails to start if installed via cloud config (on
* bug 1611973: email@example.com service not started if postgres installed
* bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades
(snapd packaging bug, but this cloud-init fix will workaround it)
* bug 1620780: dev-sda2.device job running and times out
* bug 1623570: Azure: cannot start walinux agent (Transaction order is
FIX for init-system-helpers:
REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
and service, two very central pieces of packaging infrastructure.
Errors in it will break installation/upgrades of packages or
/etc/network/if-up.d/ hooks and the like. This changes the condition
when systemd units get started without their dependencies, and the
condition gets weakened. This means that behaviour in a booted system
is unchanged, but during boot this could change the behaviour of if-
up.d/ hooks (although they have never been defined well during boot
anyway). However, I tested this change extensively in cloud images and
desktop installations (particularly I recreated
https://bugs.debian.org/777113 and confirmed that this approach also
fixes it) and could not find any regression.
TEST CASE (for both packages):
lxc launch ubuntu-daily:x --config=user.user-data="$(printf
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1
This will install all three packages, but "systemctl status
firstname.lastname@example.org" will not be running.
Now prepare a new image with the proposed cloud-init and init-system-
lxc launch ubuntu-daily:x xprep
lxc exec xprep bash
# enable -proposed and dist-upgrade, then poweroff
lxc publish xprep x-proposed
Now run the initial lxc launch again, but against that new x-proposed
image instead of the standard daily:
lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
config\npackages: [postgresql, samba, postfix]")" x1
You should now have "systemctl status email@example.com" running.
Directly after rebooting the instance, check that there are no hanging
jobs (systemctl list-jobs), particularly networking.service, to ensure
that https://bugs.debian.org/777113 did not come back.
Also test interactively installing a package that ships a service,
like "apache2", and verify that it starts properly after installation.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp