Currently there is no provision given to re-confirm which disk has been selected as 'boot disk' and which are as 'install disks' before proceeding with the partitioning and further installation of a hypervisor. Customers/users may wrongly select disks which are not intended for hypervisor installation but visible to the host (e.g LUNs) and as there is no reconfirm window showing information about selected disks. there is change to loss important data . One of our customer wrongly selected a lun which was containing large vms disks (was part of rhev storage domain) during the rhev-h installation. As there was no 'window' showing information about which disks are actually selected for host installation and to re-confirm the selection is correct. Customer simply proceed with the installation and that overwritten the disk/lun and he lost large number of virtual machines. We should provide a thread/promot/window which clearly indicates which disks have been selected as 'install disk' and 'boot disk' before proceeding with partitioning and further installation.
after confirmig with fabiand, moving to 3.5.0. need to decide if this needs cloning to 3.4.z
This is a mass change, moving bugs of merged patches into MODIFIED. Please correct the state, if you think that the move was not justified.
Verified this bug on build: Red Hat Enterprise Virtualization Hypervisor release 7.0 (20141006.0.el7ev) ovirt-node-3.1.0-0.20.20141006gitc421e04.el7.noarch Have already added a page before installation to let user make clearly which disks have been selected as 'install disk' and 'boot disk'.
This bug need more testing. Tested on rhev-hypervisor7-7.0-20150123.2 and rhev-hypervisor6-6.6-20150123.2 Boot device may be part of a storage domain! will red highlight to customer if lun already used by storage domain. Tested this on multipath iSCSI machine z600-03
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. https://rhn.redhat.com/errata/RHEA-2015-0160.html