Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-54520

kdump not generated on the Dell PowerEdge XR11

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.19.z
    • 4.19
    • GitOps ZTP
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • Rejected
    • None
    • In Progress
    • Known Issue
    • Hide
      There is a known issue where kdump vmcore file fails to save in /var/crash in the event of a crash when mlx5_core NIC driver is present in the node, due to OOM issue caused by the driver. Set 'crashkernel=1024M' for kdump to save the vmcore file successfully.
      Show
      There is a known issue where kdump vmcore file fails to save in /var/crash in the event of a crash when mlx5_core NIC driver is present in the node, due to OOM issue caused by the driver. Set 'crashkernel=1024M' for kdump to save the vmcore file successfully.
    • None
    • None
    • None
    • None

      Description of problem:

          System has kdump.service enabled configured with ACM policy and nevertheless crash dump is not generated on the node:
sh-5.1# systemctl status kdump.service
● kdump.service - Crash recovery kernel arming
     Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: disabled)
     Active: active (exited) since Wed 2025-04-02 14:13:50 UTC; 1h 18min ago
   Main PID: 3460 (code=exited, status=0/SUCCESS)
        CPU: 1.053sApr 02 14:13:49 master-0.kni-qe-69.lab.eng.rdu2.redhat.com systemd[1]: Starting Crash recovery kernel arming...
Apr 02 14:13:50 master-0.kni-qe-69.lab.eng.rdu2.redhat.com kdumpctl[3463]: kdump: kexec: loaded kdump kernel
Apr 02 14:13:50 master-0.kni-qe-69.lab.eng.rdu2.redhat.com kdumpctl[3463]: kdump: Starting kdump: [OK]
Apr 02 14:13:50 master-0.kni-qe-69.lab.eng.rdu2.redhat.com systemd[1]: Finished Crash recovery kernel arming.

      Version-Release number of selected component (if applicable):

          4.19.0-ec.4

      How reproducible:

          always

      Steps to Reproduce:

          1. standard RDS Core deployment with the kdump enabled
    2. on one of the nodes execute: echo c > /proc/sysrq-trigger
    3. wait for the node recovered from the reboot
    4. check crash folder: ls /var/crash    

      Actual results:

          the folder is empty, no kdump crash files were generated

      Expected results:

        kdump crash logs saved under /var/crash folder

      Additional info:

          1. all servers updated to the latest firmware version
    2. FDO cannot be disabled since no such config option exists (it was suggestion from the https://access.redhat.com/solutions/6977979)

              rh-ee-apalanis Abraham Miller
              elgerman Elena German
              None
              Irina Mihai
              Dwaine Gonyier Dwaine Gonyier
              None
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: