[ovirt-devel] Failed Snapshot as 'Current' after failed Live Storage Migration

[Nir Soffer]

----- Original Message -----
> From: "Christopher Pereira" <kripper at imatronix.cl>
> To: devel at ovirt.org
> Sent: Tuesday, August 4, 2015 3:58:10 AM
> Subject: [ovirt-devel] Failed Snapshot as 'Current' after failed Live	Storage Migration
> 
> Hi,
> 
> A live storage migration task failed due to a network error:
> 
> 
> 2015-08-03 21:23:16,437 WARN
> [org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand]
> (org.ovirt.thread.pool-12-thread-45) [] Could not perform live snapshot due
> to error, VM will still be configured to the new created snapshot:
> VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> VDSGenericException: VDSNetworkException: Message timeout which can be
> caused by communication issues (Failed with error VDS_NETWORK_ERROR and code
> 5022)
> 2015-08-03 21:23:16,450 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-12-thread-45) [] Correlation ID: null, Call Stack:
> org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
> VDSGenericException: VDSNetworkException: Message timeout which can be
> caused by communication issues (Failed with error VDS_NETWORK_ERROR and code
> 5022)
> at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:117)
> at
> org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33)
> at org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2029)
> at
> org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand$2.runInTransaction(CreateAllSnapshotsFromVmCommand.java:400)
> ...
> As a consequence, Engine is showing a failed snapshot as "Current", while
> libvirt is still reporting the previous correct snapshot.
> I guess next time Engine will probably try to resume the failed snapshot and
> VM won't start anymore.

Why guess? did you try this?

> What is the correct way to solve this issue?

I would restart engine, it may have bad cache.

> BZ:
> https://bugzilla.redhat.com/show_bug.cgi?id=1018867

Thanks, we will look into this.

Nir