Red Hat Bugzilla – Bug 843001
RHEV-H install failed to wipe lvm if the exist VG spans multiple disks
Last modified: 2016-04-26 11:19:16 EDT
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):
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.
1. RHEV-H install failed with reinstall / uninstall parameters.
2. RHEV-H install still failed even without any parameters.
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
PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup lvm2 a-- 3.25g 0
/dev/sdb1 VolGroup lvm2 a-- 465.76g 0
VG #PV #LV #SN Attr VSize VFree
VolGroup 2 3 0 wz--n- 469.00g 0
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
RHEV-H install can successful even the exist VG spans multiple disks
If install RHEV-H spans multiple disks, and then install RHEV-H can successful with reinstall / uninstall parameters or without any parameters.
Created attachment 600247 [details]
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.