[Bug 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances

[Dimitri John Ledkov]

systemd reboots fine in bare metal, qemu, canonistack instances (both ssh reboot & nova reboot).
the boot-smoke/bsystemd-fsckd tests pass on ppc64el.
these tests also pass on amd64/i386 qemu runner when executed with env FORCE_REBOOT_TEST=1 variable.

Dropping block-proposed tag for 234-2ubuntu5 upload, and will be re-
added again to force manual test run of the above mentioned two tests on
any future uploads.

** Attachment added: "234-2ubuntu5.tar.xz"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+attachment/4933788/+files/234-2ubuntu5.tar.xz

** Tags removed: block-proposed

** Bug watch added: github.com/systemd/systemd/issues #6614
   https://github.com/systemd/systemd/issues/6614

-- 
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