Bug 1289339 - kdump local test not detecting reboot
Summary: kdump local test not detecting reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: brose
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On: 1274469
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-07 21:37 UTC by Brian Brock
Modified: 2017-04-23 03:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-23 03:09:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brian Brock 2015-12-07 21:37:31 UTC
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):
redhat-certification-2.1-20151204.el7.noarch
redhat-certification-hardware-1.7.1-20151113.el7.noarch


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
 127.0.0.1-2015-12-07-16:19:20 took 0:00:00
 Found kdump image: /var/crash/0f77d8b2-9d28-11e5-9ae1-2c44fd1f187e/127.0.0.1-2015-12-07-16:19:20/vmcore
       KERNEL: /usr/lib/debug/lib/modules/3.10.0-327.el7.x86_64/vmlinux
     DUMPFILE: /var/crash/0f77d8b2-9d28-11e5-9ae1-2c44fd1f187e/127.0.0.1-2015-12-07-16:19:20/vmcore  [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.