kdump - sysrq-c: ERROR: No vmcore-dmesg.txt saved in /var/crash

Snippet of test failure

# https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-public/2022/08/05/redhat:605371867/build_x86_64_redhat:605371867_x86_64_debug/tests/4/results_0001/job.01/recipes/12397851/tasks/5/logs/taskout.log
[  23:24:46  ] :: [  LOG  ] :: Restarting Kdump service.
Uploading kdump.conf .done
Uploading kdump .done
kdump: Reserved 256MB memory for crash kernel
kdump: kexec: unloaded kdump kernel
kdump: Stopping kdump: [OK]
kdump: No kdump initial ramdisk found.
kdump: Rebuilding /boot/initramfs-5.19.0kdump.img
kdump: kexec: loaded kdump kernel
kdump: Starting kdump: [OK]
kdump: Kdump is operational
Uploading kdump.log .done
[  23:26:04  ] :: [  LOG  ] :: Alert: Triggering crash
use_pty:FALSE /usr/share/restraint/plugins/run_task_plugins bash ./runtest.sh
mkdir: cannot create directory ‘/mnt/testarea/’: File exists
Disable AVC check
[  23:28:23  ] :: [  LOG  ] :: Checking dumped file: vmcore-dmesg.txt
[  23:28:23  ] :: [  RUN  ] :: # find /var/crash
/var/crash
[  23:28:23  ] :: [ ERROR ] :: No vmcore-dmesg.txt saved in /var/crash. Please check kdump process in console.log
[  23:28:23  ] :: [  LOG  ] :: Checking dumped file: vmcore
[  23:28:23  ] :: [  RUN  ] :: # find /var/crash
/var/crash
[  23:28:23  ] :: [ ERROR ] :: No vmcore saved in /var/crash. Please check kdump process in console.log
:::::::::::::::::::::::::::::::::::::::::::::
:: RESULT: FAIL (skip: 0 warn: 0 error: 2)
:::::::::::::::::::::::::::::::::::::::::::::

Test logs on DataWarehouse

• Test : https://datawarehouse.cki-project.org/kcidb/tests/4719413
  • Beaker XML : https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/605371867/setup%20x86_64%20debug/2817272656/artifacts/beaker.xml

DataWarehouse issue

• DW issue : https://datawarehouse.cki-project.org/issue/1515
  • Regex : https://datawarehouse.cki-project.org/issue/-/regex/1488

Additional details

N/A

In case opening the links above result in a 404 page on DataWarehouse, please make sure you are correctly logged into DataWarehouse via Red Hat SSO.