kdump_remote

The kdump_remote test verifies that the system can capture a valid vmcore after a crash. It also verifies that the system can store the vmcore on a remote NFS share.

What the test covers
The kdump_remote test uses kdump to verify that the system captures a valid vmcore file after a crash. It also verifies that the system can store the file on a remote Network File System (NFS).
RHEL version supported
  • RHEL 8
  • RHEL 9
  • RHEL 10
What the test does

The test performs the following tasks:

  • Mounts the /var/rhcert/export filesystem on the HUT at the /var/crash directory. This filesystem is shared over NFS from the test server.
  • Crashes the host under test (HUT).
  • Writes a vmcore file to the /var/crash directory on the remote test server.
  • Validates the vmcore file.
Preparing for the test
  • Ensure that the HUT is connected to the test server before running the test.
  • Ensure the rhcertd process is running on the test server. The certification test suite prepares the NFS filesystem automatically. If the suite cannot set up the environment, the test fails.
Running the test
  1. Log in to the HUT.
  2. Run the following command:
    # rhcert-run
  3. Select the kdump_remote test.
  4. On the test server, run:
    # rhcertd start
  5. Wait for the HUT to restart after the crash. The kdump service displays messages while saving the vmcore file to the /var/crash directory. After the vmcore file is saved, the HUT restarts.
  6. After you log in to the HUT following the reboot, the rhcert suite verifies if the vmcore file exists and is valid. If the file does not exist or is invalid, the test fails.
Run time

The run time of the kdump_remote test varies depending on several factors. These factors include the amount of RAM in the HUT, disk speed of the test server, network connection speed, and reboot time.

For example, consider a 2013-era workstation with 8 GB of RAM and a 7200 RPM 6 Gb/s SATA drive. With a gigabit Ethernet connection and a 1.5-minute reboot time, the test completes in approximately five minutes. Any other mandatory pre-and post-run tests contribute to the overall runtime.