[Bug 2081020] Autopkgtest regression report (initramfs-tools/0.142ubuntu25.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted initramfs-tools (0.142ubuntu25.3) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/2.2.2-0ubuntu9 (s390x)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#initramfs-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2081020

Title:
  initrd: Ubuntu 24.04 fails to boot on UFS storage

Status in OEM Priority Project:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Noble:
  Fix Committed

Bug description:
  [Summary]

  Boot into initramfs after install 24.04 on UFS storage

  [Steps to reproduce]

  1. install ubuntu 24.04 on device with UFS storage
  2. reboot

  As additional SRU test:

  1. Store the list of files in the initrd before the package update:
  3cpio -t /boot/initrd.img > before
  2. Upgrade initramfs-tools to the fixed version
  3. Store the list of files in the initrd afterwards:
  3cpio -t /boot/initrd.img > after
  4. Compare the content of the initrd:
  diff -u before after
  5. The diff should only show (six) new kernel modules from drivers/ufs/host

  [Expected result]

  Boot into ubuntu desktop

  [Actual result]

  Boot into initramfs

  [Failure rate]

  100%

  [ Where problems could occur ]

  The initrd size will increase by 80 kB (see comment #6) and should not
  trigger people to run out of disk space.

  Generating the initrd during package upgrade could fail due to
  unrelated bugs, lack of disk space, or hardware failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081020/+subscriptions