Bug 1289339 - kdump local test not detecting reboot
kdump local test not detecting reboot
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: brose
Brian Brock
Depends On: 1274469
  Show dependency treegraph
Reported: 2015-12-07 16:37 EST by Brian Brock
Modified: 2017-04-22 23:09 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-04-22 23:09:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Brock 2015-12-07 16:37:31 EST
Description of problem:
The kdump local test fails with a complaint that it could not detect reboot, even after the system successfully rebooted.

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

How reproducible:
reliable on at least one system

Steps to Reproduce:
1. run the kdump local test on a hardware certification
2. allow the system to reboot
3. check the results when the system has rebooted and then completes the info test

Actual results:
 <output name="verify">
 reboot took 00:02:00
 method: panic
 kernel: 3.10.0-327.el7.x86_64
 Error: could not detect reboot
 Looking for vmcore image directories under /var/crash/0f77d8b2-9d28-11e5-9ae1-2c44fd1f187e took 0:00:00
 Found kdump image: /var/crash/0f77d8b2-9d28-11e5-9ae1-2c44fd1f187e/
       KERNEL: /usr/lib/debug/lib/modules/3.10.0-327.el7.x86_64/vmlinux
     DUMPFILE: /var/crash/0f77d8b2-9d28-11e5-9ae1-2c44fd1f187e/  [PARTIAL DUMP]

Expected results:
kdump test passes

Additional info:
continuing to check for any other kdump failures.  System has > 400 GB free space, reboots as expected, launchs rhcert daemons on its own.

Note You need to log in before you can comment on or make changes to this bug.