debcrafters-packages team mailing list archive

[Simon Chopin <2116165@xxxxxxxxxxxxxxxxxx>]

While the proposed solution of changing the order of things would reduce
the chances of things going wrong as described, it's not a panacea:
there's a chance the GA kernel would be also brought in within that
transaction. It's highly unlikely, granted, but it could happen.

I think there's two things that should occur here:
1/ adjust autopkgtest operation order
2/ think of a better way for users to decide which kernel they'll boot on and implement that in zipl ;)

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to s390-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2116165

Title:
  Failing to boot requested kernel on s390x

Status in autopkgtest package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  This problem is exposed by a combination of conditions:
  - For s390x arch (because of bootloader used (zipl))
  - Attempting to test an HWE kernel (version > initially released version)
  - Deployment start based on a LTS server image using the GA (initially
    released) kernel

  The special way zipl works is that it only maintains the most recently
  installed kernel as the one to use by default on next boot and the
  kernel used before as the alternative fallback. So the order of
  installing kernels matters.

  Deployment of ADT test environments seem to start based on an image that uses the initially released kernel (GA kernel). This is done by selecting the linux-generic meta. The next step seems to be to install the packages for which testing was requested (triggers). When we try to test the HWE kernel this might install a version of the kernel which is higher than the base image kernel. When this step completes the HWE kernel is the most recently installed one and the GA kernel is the previously installed one. At this point a reboot would come up with the kernel to test.
  Following the trigger installation however there is a dist-upgrade run for the deployed system. And quite often there is an updated GA kernel available as well. Which then becomes the most-recently installed one and rebooting after this comes up with the GA kernel and not the HWE kernel requested by the trigger.

  This causes the test run to be matched against the wrong kernel and
  the HWE kernel reports testing to be missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2116165/+subscriptions