Description of problem: New VM created as HA with lease could not be run with Run Once for installing OS . Fails with error as even there are no available host , but it is not the case - there is a host . Version-Release number of selected component (if applicable): ovirt-engine-4.1.8.2-0.1.el7.noarch How reproducible:100% Steps to Reproduce: 1.create new VM (disk , network,), check HA with lease = iscsi_0. 2.Open Run Once , Boot Options, Choose Network (pxe), OK in the window Actual results: fails with error saying that there is no available host (engine.log and vdsm.log attached) ERROR [org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (default task-14) [d1cb288b-7c7e-44ca-bad3-9b3a76be193e] Failed to create VM: org.ovirt.engine.core.compat.Guid cannot be cast to java.lang.String ERROR [org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (default task-14) [d1cb288b-7c7e-44ca-bad3-9b3a76be193e] Exception: java.lang.ClassCastException: org.ovirt.engine.core.compat.Guid cannot be cast to java.lang.String at org.ovirt.engine.core.vdsbroker.builder.vminfo.VmInfoBuilderImpl.buildVmBootSequence(VmInfoBuilderImpl.java:550) [vdsbroker.jar:] Expected results: no error , started to install OS Additional info:
it looks like a bug fixed only in master: https://gerrit.ovirt.org/#/c/71336/ Arik, is it the root cause?
Polina, is it reproduced only on 4.1?
May very well be. I'll backport that fix with the other patches I need to backport to the 4.1 branch.
Created attachment 1366050 [details] in engine log see line 3582
(In reply to Tomas Jelinek from comment #2) > Polina, is it reproduced only on 4.1? I didn't succeed to reproduce this on 4.2.0.0-6. only 4.1
*** Bug 1437056 has been marked as a duplicate of this bug. ***
*** Bug 1528465 has been marked as a duplicate of this bug. ***
verified in environment compute-ge-he-2.qa.lab.tlv.redhat.com version ovirt-engine-4.1.9-0.2.el7.noarch
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018. Since the problem described in this bug report should be resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.