On Tue, Apr 04, 2023 at 02:13:14PM +0800, Lichen Liu wrote:
Although upgrading the kernel with `rpm -Uvh` is not recommended, the
kexec-tools plugin prints confusing error logs when a customer upgrades the
kernel through it.
```
kdump: kernel 5.14.0-80.el9.x86_64 doesn't exist
kdump: Couldn't find current running kernel
```
Not finding the currently running kernel will only make kdump unable to copy the
grub entry parameters to the newly installed kernel, so lower the log level.
Signed-off-by: Lichen Liu <lichliu(a)redhat.com>
---
kdumpctl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kdumpctl b/kdumpctl
index 2bec428..7c32468 100755
--- a/kdumpctl
+++ b/kdumpctl
@@ -1270,7 +1270,7 @@ _find_kernel_path_by_release()
_grubby_kernel_str=$(grubby --info ALL | grep "^kernel=.*$_release\"$")
_kernel_path=$(_filter_grubby_kernel_str "$_grubby_kernel_str")
if [[ -z $_kernel_path ]]; then
- derror "kernel $_release doesn't exist"
+ ddebug "kernel $_release doesn't exist"
return 1
fi
echo -n "$_kernel_path"
@@ -1642,7 +1642,7 @@ reset_crashkernel_for_installed_kernel()
fi
if ! _running_kernel=$(_get_current_running_kernel_path); then
- derror "Couldn't find current running kernel"
+ ddebug "Couldn't find current running kernel"
exit
fi
--
2.39.2
The patch has been merged, thanks!
Reviewed-by: Coiby Xu <coxu(a)redhat.com>
--
Best regards,
Coiby