Bug 798176

Summary:	RHEV-H hung after configure kdump to unknown place.
Product:	Red Hat Enterprise Linux 6	Reporter:	cshao <cshao>
Component:	ovirt-node	Assignee:	Joey Boggs <jboggs>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	acathrow, bsarathy, jboggs, leiwang, mburns, ovirt-maint, sgordon
Target Milestone:	rc
Target Release:	6.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-node-2.3.0-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-19 14:19:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description cshao 2012-02-28 08:52:41 UTC

Description of problem:
RHEV-H hung after configure kdump to unknown place.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.2-20120227.0.el6_2

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H.
2. Configure Kdump to unknown place (e.g. 10.10.10.10:/home)
3. Run command "echo "c" > /proc/sysrq-trigger"
  
Actual results:
RHEV-H hung after run command "echo "c" > /proc/sysrq-trigger".
There is no initrd-2.6***.img generate in /boot-kdump directory.

Expected results:
RHEV-H pop-up msg "The NFS/SSH location Unreachable".

Or RHEV-H can reboot successful after run command "echo "c" > /proc/sysrq-trigger".

Additional info:

Comment 5 Mike Burns 2012-06-13 17:24:18 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No tech note needed

Comment 6 Stephen Gordon 2012-06-15 13:57:58 UTC

Deleted Technical Notes Contents.

Old Contents:
No tech note needed

Comment 8 errata-xmlrpc 2012-07-19 14:19:24 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