Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 886819 - Boot rhev-h failed with kernel panic after enabled iSCSI boot on Dell smbios 2.6+ machine
Boot rhev-h failed with kernel panic after enabled iSCSI boot on Dell smbios ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
6.4
Unspecified Unspecified
high Severity medium
: rc
: ---
Assigned To: Joey Boggs
Virtualization Bugs
:
Depends On:
Blocks: 520111
  Show dependency treegraph
 
Reported: 2012-12-13 04:10 EST by haiyang,dong
Modified: 2014-06-09 13:46 EDT (History)
13 users (show)

See Also:
Fixed In Version: ovirt-node-3.0.1-8.el6
Doc Type: Bug Fix
Doc Text:
Previously, booting rhev-h failed with a kernel panic during an enabled-iSCSI boot on Dell smbios 2.6+ machines. Booting rhev-h no longer fails with a kernel panic during an enabled-iSCSI boot on Dell smbios 2.6+ machines.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-21 14:17:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot for kernel panic after enabled iSCSI boot on Dell smbios 2.6+ machine (15.30 KB, image/png)
2012-12-13 04:10 EST, haiyang,dong
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-21 19:14:30 EST

  None (edit)
Description haiyang,dong 2012-12-13 04:10:38 EST
Created attachment 662804 [details]
Screenshot for kernel panic after enabled iSCSI boot on Dell smbios 2.6+ machine

Description of problem:
Auto install RHEV-H into  Dell smbios 2.6+ machine with "iscsi_install" parameter.
BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2008-09.com.redhat:rhevh iscsi_install iscsi_server=10.66.72.61:3260
firstboot
After auto install success, then boot rhev-h from Dell smbios 2.6+ machine.
But Boot rhev-h failed with kernel panic


Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121206.0.el6

How reproducible:
100%
  
Steps to Reproduce:
1.Auto install rhev-h with 
with "BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2008-09.com.redhat:rhevh iscsi_install iscsi_server=10.66.72.61:3260
 firstboot" parameter

Actual result:
Boot rhev-h failed with kernel panic  after enabled iSCSI boot on Dell smbios 2.6+ machine

Expect result:
Boot rhev-h success after enabled iSCSI boot on Dell smbios 2.6+ machine
Comment 11 RHEL Product and Program Management 2013-10-14 00:31:21 EDT
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 16 haiyang,dong 2013-11-05 04:42:06 EST
recent build seem to work fine, seems fixed by rebase

Test version:
rhev-hypervisor6-6.5-20131031.1
ovirt-node-3.0.1-7.el6.noarch

Auto install RHEV-H into  Dell smbios 2.6+ machine with "iscsi_install" parameter.
BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2013-02.com:hadong iscsi_install iscsi_server=10.66.11.172:3260
firstboot
After auto install success, then boot rhev-h from Dell smbios 2.6+ machine without kernel panic.
boot it and login rhev-h success.

so this bug has been fixed, i will verify it after it's status changed into
"ON_QA"

For after login rhev-h and reboot it,rhevh hanging during reboot progress issue, i have report another bug 1026702 to track it.
Comment 18 haiyang,dong 2014-01-06 21:08:15 EST
According to comment 16, change the status into "verified"
Comment 19 Cheryn Tan 2014-01-08 00:36:19 EST
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thank you for your help.
Comment 20 Charlie 2014-01-14 21:36:53 EST
Not sure if this doctext or not, thanks.
Comment 22 errata-xmlrpc 2014-01-21 14:17:18 EST
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-2014-0033.html

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