+++ This bug was initially created as a clone of Bug #965907 +++ Description of problem: There two disks on local host(seen boot_device_page.png), select the second one of the disk list as the boot/HOSTVG disk, but after install process finished, check that ovirt node still used the first one of the disk list on boot_device_pag as boot disk, not the user selected disk(seen progress_page.png). Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.0-1.0.20130517.fc18.iso How reproducible: 100% Steps to Reproduce: Actual result: ovirt node always use the first one of the disk list on boot_device_pag as boot disk Expect result: ovirt node should use the user selected disk as boot disk on boot_device_page Additional info: --- Additional comment from haiyang,dong on 2013-05-21 21:35:57 EDT ---
Also can reproduce it in the follow rhev-h version rhev-hypervisor6-6.5-20130222.0.auto1710.el6 ovirt-node-3.0.0-1.999.20130702120359git0015156.el6.noarch, so need clone it from upstream bug Component to downstream Component in order to also track it in rhev-h
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 Now it could use the user selected disk as boot disk on boot_device_page. so this bug has been fixed. I will verify it after the status changed from "MODIFIED" to "ON_QA".
According to comment 5, Change the status into "VERIFIED".
This bug will be cloned to 6.5.z, and its flag is rhel-6.6.0, so change it back to 'ON_QA', we need to test it on rhevh6.6 build.
Test version: rhev-hypervisor6-6.6-20141107.0.iso ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el6.noarch Now it could use the user selected disk as boot disk on boot_device_page. so this bug has been fixed in in rhevh 6.6 for RHEV 3.5 bulid version, 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. https://rhn.redhat.com/errata/RHEA-2015-0160.html