Bug#1079080: initramfs-tools: does not catch errors from dracut-install
Package: initramfs-tools
Version: 0.143.1
Severity: important
X-Debbugs-CC: bdrung@debian.org
In the light of the recent kmod/dracut-install issue, it came to
light that initramfs-tools does not catch errors from
dracut-install. Instead it just continues and produces an initramfs
with no modules.
As an example, with the currently broken kmod/dracut-install, on
upgrades this happens:
Setting up linux-image-6.10.4-amd64 (6.10.4-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.10.4-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.10.4-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.10.4-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.10.4-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.10.4-amd64
W: No zstd in /usr/bin:/sbin:/bin, using gzip
/usr/lib/dracut/dracut-install: symbol lookup error: /usr/lib/dracut/dracut-install: undefined symbol: kmod_module_get_weakdeps, version LIBKMOD_5
/usr/lib/dracut/dracut-install: symbol lookup error: /usr/lib/dracut/dracut-install: undefined symbol: kmod_module_get_weakdeps, version LIBKMOD_5
/usr/lib/dracut/dracut-install: symbol lookup error: /usr/lib/dracut/dracut-install: undefined symbol: kmod_module_get_weakdeps, version LIBKMOD_5
Setting up gcc-13 (13.3.0-5) ...
...
Instead, it would be good if initramfs-tools would either abort, or
at least detect the problem and refuse to overwrite an existing
initrd.img with a now broken image.
Thanks for considering!
Chris
Reply to: