This bug was fixed in the package initramfs-tools - 0.136ubuntu6.3
---------------
initramfs-tools (0.136ubuntu6.3) focal; urgency=medium
* scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
The function _log_msg() is "void" typed, returning whatever its
last command returns. This function is the basic building block
for all error/warning messages in initramfs-tools. If a bad console
is provided to kernel on command-line, printf returns error, and so
this error is carried over in _log_msg(). Happens that checkfs()
function has a loop that runs forever in this scenario (*if* fsck
is not present in initramfs and "quiet" is not passed in the
command-line). If that happens, boot is stuck and cannot progress.
The simple fix hereby merged is to return zero on _log_msg().
* scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
Currently, if an encrypted rootfs is configured on top of a MD RAID1
array and such array gets degraded (like a member is removed/failed),
initramfs-tools cannot mount the rootfs and the boot fails. We fix
that issue here by allowing cryptroot script to re-run on local-block
stage, given that mdadm is able to activate a degraded array in that
point. There is a cryptsetup counter-part for this fix, but alone the
initramfs-tools portion is innocuous.
* d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)
-- gpicc...@canonical.com (Guilherme G. Piccoli) Mon, 31 Aug 2020
13:43:29 -0300
** Changed in: initramfs-tools (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1893675
Title:
Autopkgtest failure on latest version of initramfs-tools - lack of
partprobe
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Focal:
Fix Released
Status in initramfs-tools source package in Groovy:
Fix Released
Bug description:
[Impact]
* Currently the initramfs-tools autopkgtest fails for at least AMD64, with
the following signature:
"mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device
/dev/loop0p1 does not exist."
* The reason for that is the test trying immediately to use that
partition on the loop device, but kernel may not have a partition re-
read ioctl issued, so the test may fail as observing a nonexistent
partition.
* The fix proposed here is just to manually run "partprobe" before
using the new to-be-discovered loop partition in the net autopkgtest.
[Test Case]
* Run the autopkgtest suite in the initramfs-tools package and observe the
failure aforementioned.
[Regression Potential]
* Extremely low potential, we are just introducing a partition re-read/probe
operation during autopkgtest phase, in order to keep the partition table of
loop devices consistent before the test uses it.
* The only potential issue I see with that is if for some reason we don't
have partprobe in the autopkgtest environment, but that shouldn't happen since
parted package is on ubuntu-standard.
* Notice that this test is not executed in Debian CI given that CI has
no support for VMs, and this test requires that. [See the
Rectification below]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+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
