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.
Description of problem:
Install RHEL OS spans multiple disks first, and then install RHEV-H.
RHEV-H install failed with reinstall / uninstall parameters.
RHEV-H install still failed even without any parameters.
If install RHEL into one PV, and then install RHEV-H can successful.
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120710.0.el6_3
How reproducible:
100%
Steps to Reproduce:
1. Install RHEL OS spans multiple disks first.
2. TUI install RHEV-H with reinstall / uninstall parameters.
3. TUI install RHEV-H without any parameters.
4. Focus on install process.
Actual results:
1. RHEV-H install failed with reinstall / uninstall parameters.
2. RHEV-H install still failed even without any parameters.
==================================
# lvs
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
lv_home VolGroup -wi-ao-- 411.25g
lv_root VolGroup -wi-ao-- 50.00g
lv_swap VolGroup -wi-ao-- 7.75g
]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup lvm2 a-- 3.25g 0
/dev/sdb1 VolGroup lvm2 a-- 465.76g 0
# vgs
VG #PV #LV #SN Attr VSize VFree
VolGroup 2 3 0 wz--n- 469.00g 0
ovirt.log
===============
ERROR - storage - The volume group "Bmn3BA-W84s-ne3e-bfYf-MCu4-aAz8-vdyVLv" spans multiple disks.
ERROR - storage - This operation cannot complete. Please manually cleanup the storage using standard disk tools.
ERROR - storage - Wiping LVM on /dev/mapper/1ATA_WDC_WD5000AAKS-75V0A0_WD-WCAWF6238839 Failed
Expected results:
RHEV-H install can successful even the exist VG spans multiple disks
Additional info:
If install RHEV-H spans multiple disks, and then install RHEV-H can successful with reinstall / uninstall parameters or without any parameters.
This is working as designed.
The default action of reinstall/uninstall is to wipe HostVG devices. In the case of a RHEL install with a VG not named HostVG, the user can specify storage_init=/dev/sda,/dev/sdb and we'll wipe those devices directly.
If it's not HostVG and not specified in storage_init, then we assume that we cannot do anything with those devices. This assumption is to avoid possible data loss in the event those are shared disks, or if the machine is dual boot, or some other situation where the data is needed, we require the admin to specify all disks being wiped.
In the event that the user wants to wipe /dev/sda and /dev/sdb but only install RHEVH on /dev/sda, then they will need to run uninstall against /dev/sda,/dev/sdb and then install separately.