<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 7, 2018 at 5:20 PM, Arik Hadas <span dir="ltr">&lt;<a href="mailto:ahadas@redhat.com" target="_blank">ahadas@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Mar 7, 2018 at 4:11 PM, Jan Siml <span dir="ltr">&lt;<a href="mailto:jsiml@plusline.net" target="_blank">jsiml@plusline.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
we have upgrade one of our oVirt engines to 4.2.1 (from 4.1.9) and afterwards all nodes too. The cluster compatibility level has been set to 4.2.<br>
<br>
Now we can&#39;t start a VM after it has been powered off. The only hint we found in engine.log is:<br>
<br>
2018-03-07 14:51:52,504+01 INFO [org.ovirt.engine.core.vdsbrok<wbr>er.UpdateVmDynamicDataVDSComma<wbr>nd] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] START, UpdateVmDynamicDataVDSCommand( UpdateVmDynamicDataVDSCommandP<wbr>arameters:{hostId=&#39;null&#39;, vmId=&#39;a7bc4124-06cb-4909-9389-<wbr>bcf727df1304&#39;, vmDynamic=&#39;<a href="http://org.ovirt.engine.co" target="_blank">org.ovirt.engine.co</a><wbr>re.common.businessentities.VmD<wbr>ynamic@491983e9&#39;}), log id: 7d49849e<br>
2018-03-07 14:51:52,509+01 INFO [org.ovirt.engine.core.vdsbrok<wbr>er.UpdateVmDynamicDataVDSComma<wbr>nd] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] FINISH, UpdateVmDynamicDataVDSCommand, log id: 7d49849e<br>
2018-03-07 14:51:52,531+01 INFO [org.ovirt.engine.core.vdsbrok<wbr>er.CreateVDSCommand] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] START, CreateVDSCommand( CreateVDSCommandParameters:{ho<wbr>stId=&#39;0add031e-c72f-473f-ab2f-<wbr>4f7abd1f402b&#39;, vmId=&#39;a7bc4124-06cb-4909-9389-<wbr>bcf727df1304&#39;, vm=&#39;VM [prod-hub-201]&#39;}), log id: 4af1f227<br>
2018-03-07 14:51:52,533+01 INFO [org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] START, CreateBrokerVDSCommand(HostNam<wbr>e = prod-node-210, CreateVDSCommandParameters:{ho<wbr>stId=&#39;0add031e-c72f-473f-ab2f-<wbr>4f7abd1f402b&#39;, vmId=&#39;a7bc4124-06cb-4909-9389-<wbr>bcf727df1304&#39;, vm=&#39;VM [prod-hub-201]&#39;}), log id: 71dcc8e7<br>
2018-03-07 14:51:52,545+01 ERROR [org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] Failed in &#39;CreateBrokerVDS&#39; method, for vds: &#39;prod-node-210&#39;; host: &#39;prod-node-210&#39;: null<br>
2018-03-07 14:51:52,546+01 ERROR [org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] Command &#39;CreateBrokerVDSCommand(HostNa<wbr>me = prod-node-210, CreateVDSCommandParameters:{ho<wbr>stId=&#39;0add031e-c72f-473f-ab2f-<wbr>4f7abd1f402b&#39;, vmId=&#39;a7bc4124-06cb-4909-9389-<wbr>bcf727df1304&#39;, vm=&#39;VM<br>
[prod-hub-201]&#39;})&#39; execution failed: null<br>
2018-03-07 14:51:52,546+01 INFO [org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] FINISH, CreateBrokerVDSCommand, log id: 71dcc8e7<br>
2018-03-07 14:51:52,546+01 ERROR [org.ovirt.engine.core.vdsbrok<wbr>er.CreateVDSCommand] (EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b5<br>
4a-56d9-4708-8a67-5609438ddadb<wbr>] Failed to create VM: java.lang.NullPointerException<br>
at org.ovirt.engine.core.vdsbroke<wbr>r.builder.vminfo.LibvirtVmXmlB<wbr>uilder.lambda$writeInterfaces$<wbr>23(LibvirtVmXmlBuilder.java:10<wbr>66)<br>
 [vdsbroker.jar:]<br>
<br>
[...]<br>
<br>
But this doesn&#39;t lead us to the root cause. I haven&#39;t found any matching bug tickets in release notes for upcoming 4.2.1. Can anyone help here?<br></blockquote><div><br></div></span><div>What&#39;s the mac address of that VM?</div><div>You can find it in the UI or with:</div><div><p style="margin:0px;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span style="font-variant-ligatures:no-common-ligatures">select mac_addr from vm_interface where vm_guid in (select vm_guid from vm_static where vm_name=&#39;&lt;vm_name&gt;&#39;);</span></p></div></div></div></div></blockquote><div><br></div><div>Actually, different question - does this VM has unplugged network interface?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Kind regards<span class="m_6374101265801750692gmail-m_628433926602992518HOEnZb"><font color="#888888"><br>
<br>
Jan Siml<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</font></span></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>