<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 4, 2017 at 8:42 PM, Bill James <span dir="ltr"><<a href="mailto:bill.james@j2.com" target="_blank">bill.james@j2.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF">
I have a hardware node that for whatever reason most of the VM
status was "?", even though VM was up and running fine.<br></div></blockquote><div><br></div><div>This indicates that the engine failed to monitor the host (thus switching VMs it knew that were running on it to the 'unknown' state).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF">
node was running ovirt 3.6 so I decided to upgrade it to 4.1.0.4-1
like most of the rest of the cluster is, including engine.<br>
After upgrade some VMs I'm able to start up fine on the upgraded
hosts, other fail to start on that host and migrate themselves to
another host.<br>
If I try to manually migrate them to the recently upgraded host
migration fails. I have yet to find in the logs where it says why
they fail.<br>
I am able to "runonce" the VM and tell it to start on this host and
it starts fine.<br>
Why is migration failing? </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF">
<br>
ovirt-engine-4.1.0.4-1.el7.<wbr>centos.noarch<br>
vdsm-4.19.4-1.el7.centos.x86_<wbr>64<br>
<br>
<br>
2017-03-04 10:16:51,716-08 ERROR
[org.ovirt.engine.core.dal.<wbr>dbbroker.auditloghandling.<wbr>AuditLogDirector]
(org.ovirt.thread.pool-7-<wbr>thread-48)
[519095c3-83ed-4478-8dd4-<wbr>f432db6db140] EVENT_ID:
VM_MIGRATION_TO_SERVER_FAILED(<wbr>120), Correlation ID: 2<br>
6d1ecba-8711-408d-b9d5-<wbr>6461a4aab4e5, Job ID:
546e0e11-9b4b-48d4-bd50-<wbr>2f525d049ae2, Call Stack: null, Custom Event
ID: -1, Message: Migration failed (VM: <b><a href="http://j2es2.test.j2noc.com" target="_blank">j2es2.test.j2noc.com</a></b>,
Source: <a href="http://ovirt6.test.j2noc.com" target="_blank">ovirt6.test.j2noc.com</a>, Destination: <b><a href="http://ovirt4.test.j2noc.com" target="_blank">ovirt4.test.j2noc.com</a></b>)<br>
<br>
<br>
(engine.log attached)<br></div></blockquote><div><br></div><div>The engine log doesn't contain the reason.</div><div>Please file a bug (<a href="https://bugzilla.redhat.com">https://bugzilla.redhat.com</a>) and attach VDSM logs from the mentioned source and destination hosts that cover the time of the migration attempt.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF">
<br>
Thanks.<br>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>