Created attachment 976523 [details] ovirt.log from a failed attempt Description of problem: The installation fails with "Failed to set install bootloader", but it actually fails to label the root filesystem. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.0-20150105.0.1 How reproducible: sometimes Steps to Reproduce: 1. Create a VM with a multipathed disk on a SATA bus 2. Install RHEV-H 3. Actual results: Installation failes Expected results: Installation completes Additional info:
Created attachment 976525 [details] Some command outputs
I tried this case about ten times, couldn't reproduce it in rhev-hypervisor7-7.0-20150105.0. Test steps: 1. Create a VM with a multipathed disk on a SATA bus(Create two disks in virt manager, pointing to the same disk image, and both disks need the same serial number) 2. Install RHEV-H
According to comment 4, Virt QE tested 10 times, can not reproduce it, so far we can not easy qa_ack+. it's related probability bug. What is standard to verify this bug? How many test execution if can not reproduce this bug, then this bug can safe verified?
10 times is good number of tries. Especially when it was tried on different hardware. This bug is a race, so it is hard to reproduce. I'd say, if you not encounter any "failed to install bootlader" message in your testing, then we can see this bug as verified.
haiyang, please verify this bug according to comment 6. here i pasted my test comment here FYI only: Tested on z600-03, 3 times on TUI installation with rhev-hypervisor7-7.0-20150114.0, all successful, no encounter failed to set bootloader error.
Test version: rhev-hypervisor7-7.0-20150127.0.iso ovirt-node-3.2.1-6.el7.noarch Test steps: 1. Create a VM with a multipathed disk on a SATA bus(Create two disks in virt manager, pointing to the same disk image, and both disks need the same serial number) 2. Install RHEV-H I still couldn't reproduce it in rhev-hypervisor7-7.0-20150127.0.iso and also according to Comment 9, verified this bug.
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