Bug 812865

Summary: Kdump doesn't work after configure the remote nfs server
Product: Red Hat Enterprise Linux 6 Reporter: shine <shcao>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: acathrow, bsarathy, cshao, gouyang, jboggs, leiwang, mburns, ovirt-maint, sgordon, ycui, yuachen
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.3.0-6.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 823646 (view as bug list) Environment:
Last Closed: 2012-07-19 14:11:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 817157    
Bug Blocks: 823646    
Attachments:
Description Flags
KdumpDoesntWorkPictures
none
kdump log none

Description shine 2012-04-16 13:02:25 UTC
Created attachment 577710 [details]
KdumpDoesntWorkPictures

Description of problem:
 Kdump doesn't work after configure the remote nfs server


 Version-Release number of selected component (if applicable):
 rhev-hypervisor6-6.3-20120411.1

 How reproducible:
 100%

 Steps to Reproduce:
 1. Install rhevh on local host
 2. Configure network
 3. Scroll down to Kernel Dump, choose setup nfs configuration
 4. Enter the nfs server address, and confirm the input address;[attachment RemoteNFS.png]
 5. Change to shell mode, and input "echo c > /proc/sysrq-trigger", to make the system coredump;
 6. After the system reboot, check the dump file on the remote nfs input before.

 Actual results:
 There is folder nfs:/path/var/crash in the nfs directory.
 But there is no dump file named with the dump time.
 [attachment NoDumpFile.png]

 Expected results:
 There is dump file named with the dump time in the nfs:/path/var/crash.

 Additional info:
 This a regression test.

Comment 3 shine 2012-04-17 07:50:52 UTC
ps: The kdump works well in the last build: rhev-hypervisor6-6.3-20120409.0.el6_2.

Comment 4 shine 2012-04-17 07:54:13 UTC
ps: The kdump works well in the last build: rhev-hypervisor6-6.3-20120409.0.el6_2.

Comment 5 shine 2012-04-17 07:57:22 UTC
(In reply to comment #3)
> ps: The kdump works well in the last build:
> rhev-hypervisor6-6.3-20120409.0.el6_2.

Sorry there is a mistake about the name of the last build.
It should be rhev-hypervisor6-6.3-20120330.0.el6.

Comment 6 shine 2012-04-17 07:57:49 UTC
(In reply to comment #4)
> ps: The kdump works well in the last build:
> rhev-hypervisor6-6.3-20120409.0.el6_2.

Sorry there is a mistake about the name of the last build.
It should be rhev-hypervisor6-6.3-20120330.0.el6.

Comment 8 shine 2012-04-18 06:50:05 UTC
Created attachment 578249 [details]
kdump log


The attachment Kdump6.3  is the log grabbed through serial console on two rhevh versions.
I have tried the tests on the same machine with the same nfs storage path, but the different rhevh version.
The kdump works well on the last rhevh version:  6.3-20120330.0.el6.
The kdump couldn't get a DHCP address retRestarting system on the rhevh 6.3-20120411.1; so there is no the dump file named with host-name and dump time on the nfs storage.

Comment 18 errata-xmlrpc 2012-07-19 14:11:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0741.html