kdump-tools won't create initrd for previously installed kernels
Bug #1751328 reported by
Thadeu Lima de Souza Cascardo
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
makedumpfile (Ubuntu) |
Fix Released
|
Medium
|
Thadeu Lima de Souza Cascardo | ||
Bug Description
When kdump-tools is installed, it creates an initrd for the running kernel. For kernels installed after that, the postinst part will be run and a initrd will be created as well. However, for kernels that are already installed, it won't create them.
As an example, when the user is running 4.4.0-112-generic, but has 4.13.0-32-generic installed, kdump-tools will create an initrd for 4.4.0-112-generic. When the user later reboots into 4.13.0-32-generic, the initrd is not present, and kdump-tools won't load.
Cascardo.
Changed in makedumpfile (Ubuntu): | |
assignee: | nobody → Thadeu Lima de Souza Cascardo (cascardo) |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
This is now fixed in Debian. It would be nice to sync it to Bionic.