[Bug 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances
Dimitri John Ledkov
launchpad at surgut.co.uk
Tue Aug 15 12:37:01 UTC 2017
$ cat logs-amd64/summary
timedated PASS
hostnamed PASS
localed-locale PASS
localed-x11-keymap PASS
logind PASS
unit-config PASS
storage PASS
networkd-test.py PASS
build-login PASS
boot-and-services PASS
udev PASS
root-unittests PASS
upstream PASS
boot-smoke PASS
systemd-fsckd PASS
$ cat logs-i386/summary
timedated PASS
hostnamed PASS
localed-locale PASS
localed-x11-keymap PASS
logind PASS
unit-config PASS
storage PASS
networkd-test.py PASS
build-login PASS
boot-and-services PASS
udev PASS
root-unittests PASS
upstream PASS
boot-smoke PASS
systemd-fsckd PASS
** Tags added: adt-fail block-proposed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
New
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
More information about the foundations-bugs
mailing list