[ovirt-users] oVirt 4.2 , VM stuck in "Migrating from" state.
Arik Hadas
ahadas at redhat.com
Tue Feb 6 11:25:28 UTC 2018
Hi,
The problem you had is fixed already by https://gerrit.ovirt.org/#/c/86367/.
I'm afraid you'll need to manually set the VM to Down in the database:
update vm_dynamic set status=0 where vm_guid in (select vm_guid from
vm_static where vm_name='<vm name>')
On Tue, Feb 6, 2018 at 11:20 AM, Eduardo Mayoral <emayoral at arsys.es> wrote:
> Hi,
>
> Got a problem with oVirt 4.2
>
> While putting a Host in maintenance mode, an VM has failed to migrate.
> The end state is that the Web UI shows the VM as "Migrating from".
>
> The VM is not running in any Host in the cluster.
>
> This is the relevant message in the /var/log/ovirt-engine/engine.log
>
> 2018-02-06 09:09:05,379Z INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (EE-ManagedThreadFactory-engineScheduled-Thread-14) [] VM
> 'ab158ff3-a716-4655-9269-11738cd53b05'(repositorionuget) is running in
> db and not running on VDS
> '82b49615-9c65-4d8e-80e0-f10089cb4225'(llkh456.arsyslan.es)
> 2018-02-06 09:09:05,381Z ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-14) [] Failed during
> monitoring vm: ab158ff3-a716-4655-9269-11738cd53b05 , error is: {}:
> java.lang.NullPointerException
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> auditVmMigrationAbort(VmAnalyzer.java:440)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.abortVmMigration(
> VmAnalyzer.java:432)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> proceedDisappearedVm(VmAnalyzer.java:794)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.analyze(VmAnalyzer.
> java:135)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.lambda$
> analyzeVms$1(VmsMonitoring.java:136)
> [vdsbroker.jar:]
> at java.util.ArrayList.forEach(ArrayList.java:1255)
> [rt.jar:1.8.0_151]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.analyzeVms(
> VmsMonitoring.java:131)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.perform(
> VmsMonitoring.java:94)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll(
> PollVmStatsRefresher.java:43)
> [vdsbroker.jar:]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_151]
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [rt.jar:1.8.0_151]
> at
> org.glassfish.enterprise.concurrent.internal.
> ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(
> ManagedScheduledThreadPoolExecutor.java:383)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> org.glassfish.enterprise.concurrent.internal.
> ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(
> ManagedScheduledThreadPoolExecutor.java:534)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_151]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> at
> org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$
> ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$
> ElytronManagedThread.run(ElytronManagedThreadFactory.java:78)
>
> 2018-02-06 09:09:05,381Z ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-14) [] Exception::
> java.lang.NullPointerException
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> auditVmMigrationAbort(VmAnalyzer.java:440)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.abortVmMigration(
> VmAnalyzer.java:432)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> proceedDisappearedVm(VmAnalyzer.java:794)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.analyze(VmAnalyzer.
> java:135)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.lambda$
> analyzeVms$1(VmsMonitoring.java:136)
> [vdsbroker.jar:]
> at java.util.ArrayList.forEach(ArrayList.java:1255)
> [rt.jar:1.8.0_151]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.analyzeVms(
> VmsMonitoring.java:131)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.perform(
> VmsMonitoring.java:94)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll(
> PollVmStatsRefresher.java:43)
> [vdsbroker.jar:]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_151]
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [rt.jar:1.8.0_151]
> at
> org.glassfish.enterprise.concurrent.internal.
> ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(
> ManagedScheduledThreadPoolExecutor.java:383)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> org.glassfish.enterprise.concurrent.internal.
> ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(
> ManagedScheduledThreadPoolExecutor.java:534)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_151]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> at
> org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$
> ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$
> ElytronManagedThread.run(ElytronManagedThreadFactory.java:78)
>
> I already tried canceling the migration, powering off the VM, restarting
> the engine service and restarting the vdsm on the host which is supposed
> to have that VM. No success so far. unlock_entity.sh shows no locked
> entities.
>
> Can somebody help on how to recover from this?
>
> Thanks!
>
>
> --
> Eduardo Mayoral Jimeno (emayoral at arsys.es)
> Administrador de sistemas. Departamento de Plataformas. Arsys internet.
> +34 941 620 145 ext. 5153
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180206/a8edd33b/attachment.html>
More information about the Users
mailing list