This bug was fixed in the package systemd - 234-2ubuntu6 --------------- systemd (234-2ubuntu6) artful; urgency=medium
* Disable KillUserProcesses, yet again, with meson this time. * Re-enable reboot tests. -- Dimitri John Ledkov <x...@ubuntu.com> Thu, 17 Aug 2017 15:22:35 +0100 ** Changed in: systemd (Ubuntu) Status: New => 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/1708051 Title: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances Status in systemd package in Ubuntu: Fix Released Bug description: ppc64el is fine. Given that everything is fixed to start containers and vms non- degraded, let's enforce that we boot not degraded. Also network online timeout is 30s, thus it makes no sense to only give the boot 10s. Especially since machines can be overcommitted with capacity. update: tests were improved somewhat, to be more deterministic and always wait for the boot to fully finish before rebooting. On the infrastructure - all but i386/amd64 pass. But locally it is not reproducible. It almost feels like openstack-nova-autopkgtest-reboot- marker integration is broken; or systemd fails to reboot in scalingstack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+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