<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 16, 2017 at 12:56 PM, Eduardo Mayoral <span dir="ltr"><<a href="mailto:emayoral@arsys.es" target="_blank">emayoral@arsys.es</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
An interesting thing just happened on my oVirt deployment.<br>
<br>
While setting a host for maintenance, one of the VMs running on that<br>
host failed to migrate. Then ovirt-engine for some reason turned the VM<br>
off. Here are the relevant log lines from engine.log:<br>
<br>
<br>
<br>
<br>
2017-03-16 09:56:23,324Z INFO<br>
[org.ovirt.engine.core.bll.<wbr>MigrateVmCommand] (default task-60)<br>
[61a52216] Lock Acquired to object<br>
'EngineLock:{exclusiveLocks='[<wbr>422663a9-d712-4992-7c81-<wbr>165b2976073e=<VM,<br>
ACTION_TYPE_FAILED_VM_IS_<wbr>BEING_MIGRATED$VmName<br>
entorno127.arsysdesarrollo.<wbr>lan>]', sharedLocks='null'}'<br>
2017-03-16 09:56:23,957Z INFO<br>
[org.ovirt.engine.core.dal.<wbr>dbbroker.auditloghandling.<wbr>AuditLogDirector]<br>
(default task-60) [61a52216] EVENT_ID:<br>
VM_MIGRATION_START_SYSTEM_<wbr>INITIATED(67), Correlation ID: 61a52216, Job<br>
ID: fbc5e0d7-4618-4ca8-b7a7-<wbr>0fd9a43f490f, Call Stack: null, Custom Event<br>
ID: -1, Message: Migration initiated by system (VM:<br>
entorno127.arsysdesarrollo.<wbr>lan, Source: <a href="http://llkk594.arsyslan.es" rel="noreferrer" target="_blank">llkk594.arsyslan.es</a>,<br>
Destination: <a href="http://llkk593.arsyslan.es" rel="noreferrer" target="_blank">llkk593.arsyslan.es</a>, Reason: Host preparing for maintenance).<br>
2017-03-16 09:56:26,818Z INFO<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>VmAnalyzer]<br>
(DefaultQuartzScheduler10) [7c6c403b-0a82-47aa-aeb4-<wbr>57fbe06e20e1] VM<br>
'422663a9-d712-4992-7c81-<wbr>165b2976073e'(entorno127.<wbr>arsysdesarrollo.lan)<br>
was unexpectedly detected as 'MigratingTo' on VDS<br>
'43f43ec5-e51d-400d-8569-<wbr>261c98382e3a'(<a href="http://llkk593.arsyslan.es" rel="noreferrer" target="_blank">llkk593.<wbr>arsyslan.es</a>) (expected on<br>
'11a82467-afa4-4e4e-bd92-<wbr>3383082d0a5e')<br>
2017-03-16 09:56:42,149Z INFO<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>VmAnalyzer]<br>
(DefaultQuartzScheduler10) [fac8ade9-a867-4ff7-aac5-<wbr>912f78cc3bb5] VM<br>
'422663a9-d712-4992-7c81-<wbr>165b2976073e'(entorno127.<wbr>arsysdesarrollo.lan)<br>
was unexpectedly detected as 'MigratingTo' on VDS<br>
'43f43ec5-e51d-400d-8569-<wbr>261c98382e3a'(<a href="http://llkk593.arsyslan.es" rel="noreferrer" target="_blank">llkk593.<wbr>arsyslan.es</a>) (expected on<br>
'11a82467-afa4-4e4e-bd92-<wbr>3383082d0a5e')<br>
2017-03-16 09:56:54,755Z INFO<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>VmAnalyzer]<br>
(DefaultQuartzScheduler3) [54fa9a1b-fddb-4812-b5d2-<wbr>06cf92834709] VM<br>
'422663a9-d712-4992-7c81-<wbr>165b2976073e'(entorno127.<wbr>arsysdesarrollo.lan)<br>
moved from 'MigratingFrom' --> 'Down'<br>
2017-03-16 09:56:54,755Z INFO<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>VmAnalyzer]<br>
(DefaultQuartzScheduler3) [54fa9a1b-fddb-4812-b5d2-<wbr>06cf92834709] Handing<br>
over VM<br>
'422663a9-d712-4992-7c81-<wbr>165b2976073e'(entorno127.<wbr>arsysdesarrollo.lan)<br>
to Host '43f43ec5-e51d-400d-8569-<wbr>261c98382e3a'. Setting VM to status<br>
'MigratingTo'<br>
2017-03-16 09:56:58,160Z INFO<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>VmAnalyzer]<br>
(DefaultQuartzScheduler4) [dd4ea7bb-85bc-410e-9a8f-<wbr>357c28d85d1c] VM<br>
'422663a9-d712-4992-7c81-<wbr>165b2976073e'(entorno127.<wbr>arsysdesarrollo.lan)<br>
is running in db and not running on VDS<br>
'43f43ec5-e51d-400d-8569-<wbr>261c98382e3a'(<a href="http://llkk593.arsyslan.es" rel="noreferrer" target="_blank">llkk593.<wbr>arsyslan.es</a>)<br>
2017-03-16 09:56:58,161Z INFO<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>VmAnalyzer]<br>
(DefaultQuartzScheduler4) [dd4ea7bb-85bc-410e-9a8f-<wbr>357c28d85d1c] add VM<br>
'422663a9-d712-4992-7c81-<wbr>165b2976073e'(entorno127.<wbr>arsysdesarrollo.lan)<br>
to rerun treatment<br>
turn to maintenance while VMs are still running on it.(VM:<br>
entorno127.arsysdesarrollo.<wbr>lan, Source: <a href="http://llkk594.arsyslan.es" rel="noreferrer" target="_blank">llkk594.arsyslan.es</a>,<br>
Destination: <a href="http://llkk593.arsyslan.es" rel="noreferrer" target="_blank">llkk593.arsyslan.es</a>).<br>
2017-03-16 09:56:59,193Z INFO<br>
[org.ovirt.engine.core.bll.<wbr>MigrateVmCommand]<br>
(org.ovirt.thread.pool-7-<wbr>thread-27) [14d40a88] Lock freed to object<br>
'EngineLock:{exclusiveLocks='[<wbr>422663a9-d712-4992-7c81-<wbr>165b2976073e=<VM,<br>
ACTION_TYPE_FAILED_VM_IS_<wbr>BEING_MIGRATED$VmName<br>
entorno127.arsysdesarrollo.<wbr>lan>]', sharedLocks='null'}'<br>
<br>
Now, I understand an VM migration may fail for a number of reasons, but<br>
in that case, shouldn't the VM keep running on the source host? I do not<br>
quite understand what happened here or how to avoid it in the future.<br></blockquote><div><br></div><div>Can you share vdsm logs from both source and destination?</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best regards,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Eduardo Mayoral Jimeno (<a href="mailto:emayoral@arsys.es">emayoral@arsys.es</a>)<br>
Administrador de sistemas. Departamento de Plataformas. Arsys internet.<br>
<a href="tel:%2B34%20941%20620%20145%20ext.%205153" value="+34941620145">+34 941 620 145 ext. 5153</a><br>
<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>
</font></span></blockquote></div><br></div></div>