This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2.2 --------------- kdump-tools (1:1.6.10ubuntu2.2) jammy; urgency=medium
* Disable the initramfs generation in our kernel-postinst hook when we detect we are running in a chroot. LP: #2043059. -- dann frazier <da...@ubuntu.com.org> Thu, 01 Feb 2024 07:34:55 -0700 ** Changed in: kdump-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in linux-nvidia source package in Jammy: Invalid Status in kdump-tools source package in Mantic: Fix Released Status in linux-nvidia source package in Mantic: Invalid Status in kdump-tools source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Invalid Bug description: [Impact] When installing in a chroot environment, the kdump-tools kernel hook will fail. This breaks certain OS image creation tools, such as BCM (which I assume is NVIDIA Base Command Manager from context). While BCM's image generation tool requires some additional tweaks to consume this, the proposed fix is necessary, and should be sufficient for other tools that use chroots. [Test Plan] 1) debootstrap a chroot environment for the target Ubuntu release 2) Install kdump-tools within that environment 3) Install a kernel package and make sure it succeeds. 4) do the same steps in a virtual machine, but with `ischroot` symlinked to /dev/true at install time. This should simulate a system that was just installed with an image prepared as above. 5) Then restore ischroot, and reboot. 6) Confirm the systemd service does generate an initramfs at boot, and 7) that a crash dump can be triggered afterwords. [Where Problems Could Occur] The solution we implemented in noble was simply to detect a chroot environment with ischroot, and disable initramfs generation. The systemd service will detect that an initrd is missing, and generate one on first boot. A source of potential problems is if that does not happen for some reason, resulting in a kdump-tools service failure on first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp