<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 7, 2018 at 5:32 PM, Jan Siml <span dir="ltr"><<a href="mailto:jsiml@plusline.net" target="_blank">jsiml@plusline.net</a>></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 Arik,<br>
<br>
<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"><span class="gmail-">
we have upgrade one of our oVirt engines to 4.2.1 (from 4.1.9)<br>
and afterwards all nodes too. The cluster compatibility level<br>
has been set to 4.2.<br>
<br>
Now we can't start a VM after it has been powered off. The only<br>
hint we found in engine.log is:<br>
<br>
2018-03-07 14:51:52,504+01 INFO<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.UpdateVmDynamicDataVDSComma<wbr>nd]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] START,<br>
UpdateVmDynamicDataVDSCommand(<br>
UpdateVmDynamicDataVDSCommandP<wbr>arameters:{hostId='null',<br>
vmId='a7bc4124-06cb-4909-9389-<wbr>bcf727df1304',<br>
vmDynamic='<a href="http://org.ovirt.engine.co" rel="noreferrer" target="_blank">org.ovirt.engine.co</a><br></span>
<<a href="http://org.ovirt.engine.co" rel="noreferrer" target="_blank">http://org.ovirt.engine.co</a>>re<wbr>.common.businessentities.VmDyn<wbr>amic@491983e9'}),<div><div class="gmail-h5"><br>
log id: 7d49849e<br>
2018-03-07 14:51:52,509+01 INFO<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.UpdateVmDynamicDataVDSComma<wbr>nd]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] FINISH,<br>
UpdateVmDynamicDataVDSCommand, log id: 7d49849e<br>
2018-03-07 14:51:52,531+01 INFO<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.CreateVDSCommand]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] START, CreateVDSCommand(<br>
CreateVDSCommandParameters:{ho<wbr>stId='0add031e-c72f-473f-ab2f-<wbr>4f7abd1f402b',<br>
vmId='a7bc4124-06cb-4909-9389-<wbr>bcf727df1304', vm='VM<br>
[prod-hub-201]'}), log id: 4af1f227<br>
2018-03-07 14:51:52,533+01 INFO<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] START,<br>
CreateBrokerVDSCommand(HostNam<wbr>e = prod-node-210,<br>
CreateVDSCommandParameters:{ho<wbr>stId='0add031e-c72f-473f-ab2f-<wbr>4f7abd1f402b',<br>
vmId='a7bc4124-06cb-4909-9389-<wbr>bcf727df1304', vm='VM<br>
[prod-hub-201]'}), log id: 71dcc8e7<br>
2018-03-07 14:51:52,545+01 ERROR<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] Failed in<br>
'CreateBrokerVDS' method, for vds: 'prod-node-210'; host:<br>
'prod-node-210': null<br>
2018-03-07 14:51:52,546+01 ERROR<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] Command<br>
'CreateBrokerVDSCommand(HostNa<wbr>me = prod-node-210,<br>
CreateVDSCommandParameters:{ho<wbr>stId='0add031e-c72f-473f-ab2f-<wbr>4f7abd1f402b',<br>
vmId='a7bc4124-06cb-4909-9389-<wbr>bcf727df1304', vm='VM<br>
[prod-hub-201]'})' execution failed: null<br>
2018-03-07 14:51:52,546+01 INFO<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.CreateBrokerVDSCo<wbr>mmand]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25)<br>
[f855b54a-56d9-4708-8a67-56094<wbr>38ddadb] FINISH,<br>
CreateBrokerVDSCommand, log id: 71dcc8e7<br>
2018-03-07 14:51:52,546+01 ERROR<br>
[org.ovirt.engine.core.vdsbrok<wbr>er.CreateVDSCommand]<br>
(EE-ManagedThreadFactory-engin<wbr>e-Thread-25) [f855b5<br>
4a-56d9-4708-8a67-5609438ddadb<wbr>] Failed to create VM:<br>
java.lang.NullPointerException<br>
at<br>
org.ovirt.engine.core.vdsbroke<wbr>r.builder.vminfo.LibvirtVmXmlB<wbr>uilder.lambda$writeInterfaces$<wbr>23(LibvirtVmXmlBuilder.java:<wbr>1066)<br>
[vdsbroker.jar:]<br>
<br>
[...]<br>
<br>
But this doesn't lead us to the root cause. I haven't found any<br>
matching bug tickets in release notes for upcoming 4.2.1. Can<br>
anyone help here?<br>
<br>
<br>
What's the mac address of that VM?<br>
You can find it in the UI or with:<br>
<br>
select mac_addr from vm_interface where vm_guid in (select vm_guid<br>
from vm_static where vm_name='<vm_name>');<br>
<br>
<br>
Actually, different question - does this VM has unplugged network interface?<br>
</div></div></blockquote>
<br>
The VM has two NICs. Both are plugged.<br>
<br>
The MAC addresses are 00:1a:4a:18:01:52 for nic1 and 00:1a:4a:36:01:67 for nic2.<br></blockquote><div><br></div><div>OK, those seem like two valid mac addresses so maybe something is wrong with the vm devices.</div><div>Could you please provide the output of:</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 type, device, address, is_managed, is_plugged, alias from vm_device where vm_id in (select vm_guid from vm_static where vm_name='<vm_name>');</span></p></div><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>
Regards<span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
Jan<br>
</font></span></blockquote></div><br></div></div>