Kdump fails to generate the vmcore file over nfs or ssh when fips is enabled.

Solution Verified - Updated -

Issue

  • The kdump fails to generate the vmcore over nfs or ssh when fips is enabled.
  • The system is also getting hang upon failure instead of reboot though the default action set to reboot.
  • Here is the console output from BIOS based system.
[   51.009994] systemd-udevd[747]: Using default interface naming scheme 'rhel-9.1'.
[   79.194004] dracut-pre-pivot[735]: Checking integrity of kernel
[   79.219467] dracut-pre-pivot[735]: Warning: /boot//.vmlinuz-5.14.0-162.6.1.el9_1.x86_64.hmac does not exist
[   79.852488] dracut: FATAL: FIPS integrity test failed
[   79.859432] dracut: Refusing to continue
[   79.426567] systemd[1]: Shutting down.
..

[   82.080815] systemd-shutdown[1]: Failed to finalize loop devices, ignoring.
[   82.087465] systemd-shutdown[1]: Syncing filesystems and block devices.
[   82.095373] systemd-shutdown[1]: Halting system.
[   82.121202] reboot: System halted
  • Here is the console output from UEFI based system.
[   35.009994] systemd-gpt-auto-generator[655]: EFI loader partition unknown, exiting.
[   35.009994] systemd-gpt-auto-generator[655]: (The boot loader did not set EFI variable LoaderDevicePartUUID.)
[   60.012994] dracut: FATAL: FIPS integrity test failed
[   60.019393] dracut: Refusing to continue
[   61.009994] systemd-shutdonw[1]: Syncing filesystems and block devices.

Environment

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Guest running on Hyper-v or azure
  • Guest running on VMWare ESXI
  • Guest running on Nutanix

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content