Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
After a successful TUI installation of Red Hat Enterprise Virtualization Hypervisor, passing the boot option "BOOTIF=eth0 storage_init=ata firstboot" on auto installation failed to find all components of a LVM Volume Group. The storage_init logic was modified to correctly determine where LVM components would be when a bus was provided. Two passes were introduced which parsed and translated the device names into lvm device names to allow for a comparison.
http://gerrit.ovirt.org/8811
This was a bit tricky.
To prevent the removal of VG in the case where not all of it's member PVs were given in the storage_init line a comparison is necessary.
But this comparison was to optimistic and was wrong in most cases. The problem was that the storage_init argument can contain bus names (ata, scsi, ...) as well as devices (/dev/sda). But in a Node/RHEV-H setup the PV is created on a partition, so comparing a bus or device against a partition path always failed (except the case where the partition was given in the storage_init arg).
Now the storage_init arg is "parsed" (translates bus to device) and searches for all affected partitions (for a given device) and at last translates the devname to the devname lvm is using before doing the final comparison.
So with this patch all VGs (and their member LVs) are removed in the case that all PVs which form a VG can be derived from the storage_init arg.
In other words, much stuff has changed and much can go wrong, please review with care.
Tested as follows:
1. Install RHEV-H
2. After installation reboot and boot from media again
3. Append "storage_init=ata firstboot BOOTIF=eth0" arguments and boot
4. Watch for dracut messages telling that the HostVG and LV members were removed
5. The re-installation should be initiated.
Test version:
rhev-hypervisor6-6.4-20121212.1.el6
ovirt-node-2.5.0-11.el6
Tested as follows:
BOOTIF=eth0 storage_init=ata firstboot Pass
BOOTIF=eth0 storage_init=/dev/sda firstboot Pass
BOOTIF=eth0 storage_init=/dev/mapper/360*72b0 firstboot Pass
BOOTIF=eth0 storage_init=usb firstboot Pass
so this bug has been fixed, change the status into "VERIFIED"
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
Created attachment 631932 [details] attached the ovirt.log Description of problem: Clean install rhev-h via TUI, after install it successfully, reboot it and auto install rhev-h with with "BOOTIF=eth0 storage_init=ata firstboot" parameter,but auto install failed to pvcreate HOSTVG Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20121015.1.el6 How reproducible: 100% Steps to Reproduce: 1.Insert the installation media(CD-ROM/USB), and start the system. 2.clean install rhev-h via TUI 3.After install rhev-h successfully,then reboot again, press the Tab key to append follow parameters "BOOTIF=eth0 storage_init=ata firstboot" into kernel parameters for the selected boot option. Actual result: After Step 3, Auto install RHEV-H failed to pvcreate HOSTVG cat ovirt.log ---------- 2012-10-23 07:01:48,762 - DEBUG - ovirtfunctions - multipath -r &>/dev/null 2012-10-23 07:01:48,762 - DEBUG - ovirtfunctions - 2012-10-23 07:01:48,762 - ERROR - storage - /dev/mapper/1ATA_SAMSUNG_HD322HJ_S1GXJ90S2049294 is not available! 2012-10-23 07:01:49,768 - DEBUG - ovirtfunctions - dd if=/dev/zero of="/dev/mapper/1ATA_SAMSUNG_HD322HJ_S1GXJ90S204929p4" bs=1024k count=1 2012-10-23 07:01:49,769 - DEBUG - ovirtfunctions - 2012-10-23 07:01:49,886 - DEBUG - ovirtfunctions - pvcreate -ff -y "/dev/mapper/1ATA_SAMSUNG_HD322HJ_S1GXJ90S204929p4" 2012-10-23 07:01:49,886 - DEBUG - ovirtfunctions - 2012-10-23 07:01:49,886 - ERROR - storage - Failed to pvcreate on /dev/mapper/1ATA_SAMSUNG_HD322HJ_S1GXJ90S204929p4 2012-10-23 07:01:49,887 - INFO - network - Configuring Interface Expect result: Auto install RHEV-H should success after clean install rhev-h success via TUI.