kdump does not work on Compute node with Instance HA

Solution Verified - Updated -

Issue

  • System was crashed manually to test configured kdump, but the vmcore file is not saved with the following errors.

    [...]
dracut-initqueue[226]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[226]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[226]: Warning: dracut-initqueue timeout - starting timeout scripts
[...]
dracut-initqueue[226]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[226]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[226]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[226]: Warning: Could not boot.
dracut-initqueue[226]: Warning: Not all disks have been found.
dracut-initqueue[226]: Warning: You might want to regenerate your initramfs.
[...]

Environment

  • Red Hat Enterprise Linux 7 (this issue was reported in RHEL7, but would also occur in RHEL8 or later)
    • High Availability (HA) add-on
      • fence-agents-kdump package
        • fence_kdump is configured
    • Communicate with pacemaker nodes via a VLAN interface by openvswitch (OVS)
  • Red Hat OpenStack Platform
    • Compute node with Instance HA
      • fence-agents-kdump package
        • fence_kdump is configured
    • Communicate with Controller nodes via a VLAN interface by openvswitch (OVS)

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