RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 879542 - Kernel panic occurs during auto installation if there were two PV existing
Summary: Kernel panic occurs during auto installation if there were two PV existing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-23 09:34 UTC by cshao
Modified: 2013-02-28 16:45 UTC (History)
12 users (show)

Fixed In Version: ovirt-node-2.5.0-10.el6
Doc Type: Bug Fix
Doc Text:
In an automatic installation, a kernel panic occurred when there are two or more LVM physical volumes (PV) and not all are referenced in the storage_init parameter. This fix ensures dracut shows the missing PV elements during the installation when attempting to remove LVM metadata.
Clone Of:
Environment:
Last Closed: 2013-02-28 16:45:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
kernel panic (121.13 KB, image/jpeg)
2012-12-05 02:30 UTC, cshao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0556 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2013-02-28 21:29:06 UTC

Description cshao 2012-11-23 09:34:13 UTC
Description of problem:
Kernel panic occurs during auto installation if there were two PV existing.

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

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H on two pv(e.g. ata + usb).
2. Reboot host and enter boot media.
3. Auto install RHEV-H to ata(e.g. storage_init=/dev/sda firstboot).
  
Actual results:
1. Kernel panic - not syncing: Attempted to kill init!
2. After step 2, TUI install can successful.

Expected results:
Auto install can successful without kernel panic.

Additional info:
No such issue in rhev-hypervisor6-6.3-20121121.0.el6_3 version, so it is a regression bug.

Comment 10 cshao 2012-12-05 02:30:49 UTC
Created attachment 657889 [details]
kernel panic

Upload the kernel panic screenshot from serial console for you reference.

Comment 16 errata-xmlrpc 2013-02-28 16:45:58 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-2013-0556.html


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