> But 55-initrd.install should ALSO fail when it detects missing initrd.
That's defense in depth.
I am still not sure that is right. As I said, an initrd is not strictly
needed in all settings where kernel-install is used. The current
behavior is intended.
I really think the kernel packaging should handle all of this. If *any*
of the run-parts scripts in /etc/kernel/postinst.d/ fail, the package
installation should probably fail/stop. Handling this one case won't
change that.
I am adding a task for the kernel team to take a look.
> I also noticed upstream systemd is actively making changes to
55-initrd.install around staging area handling.
I am not sure what you mean about upstream actively making changes to
55-initrd.install. That's a Debian/Ubuntu specific configuration.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141741
Title:
55-initrd.install silently exits 0 when initrd missing causing
undetectable kernel panic on NVMe systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141741/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
