Bug 798176 - RHEV-H hung after configure kdump to unknown place.
Summary: RHEV-H hung after configure kdump to unknown place.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 6.2
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 08:52 UTC by cshao
Modified: 2016-04-26 15:08 UTC (History)
7 users (show)

Fixed In Version: ovirt-node-2.3.0-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-19 14:19:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

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
Note You need to log in before you can comment on or make changes to this bug.