Red Hat Bugzilla – Bug 1258654
RFE: Extend check_rebuild() in kdumpctl to trigger a kdump initramfs image rebuild if the dump device UUID has changed.
Last modified: 2016-11-04 02:54:25 EDT
The kdump service recreates the initial ramdisk automatically if the configuration or one of the listed files has changed. We use the legacy device names in our configuration and dracut converts the legacy names to UUIDs during creating the initial ramdisk. The UUID of swap devices is changing during re-setup the swap device. kdumpctl doesn't detect this change and doesn't recreate the init ramdisk in such case.
So the customer would like kdump to trigger an initramfs image rebuild if the devices referenced in an unchanged kdump.conf have changed (i.e. rebuilding kdump initramfs image only on changed kdump.conf modification time is insufficient).
(In reply to firstname.lastname@example.org from comment #0)
> So the customer would like kdump to trigger an initramfs image rebuild if
> the devices referenced in an unchanged kdump.conf have changed (i.e.
> rebuilding kdump initramfs image only on changed kdump.conf modification
> time is insufficient).
Will it be possible by customer to test kexec-tools from the following brewbuild?
Customer confirms kexec-tools-2.0.7-38.el7.x86_64 resolves the issue. Thanks again!
Patches have been re-posted to RHEL7.3.
May generate warning like
"Kernel dev name of 192.168.122.199:/export/nfs is not found."
dracut-functions.sh defines a get_persistent_dev(). Earlier, we had another
local get_persistent_dev() in mkdumprd, however that was moved to
kdump-lib.sh, so that it can be reused in kdumpctl.
Since, dracut-module-setup.sh (which is dracut's
99kdumpbase/module-setup.sh) sources kdump-lib.sh. Therefore, once dracut
will execute 99kdumpbase module, it's own get_persistent_dev() function is
overwritten by kdump's version. If any other dracut module calls
get_persistent_dev() thereafter then, kdump's version is executed, which was
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.