3:58 a.m.
This is a multi-part message in MIME format.
--------------000701090209060705020903
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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.
What is the correct way to solve this issue?
BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1018867
--------------000701090209060705020903
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
A live storage migration task failed due to a network error:<br>
<blockquote>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)<br>
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)<br>
at
org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:117)<br>
at
org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33)<br>
at
org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2029)<br>
at
org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand$2.runInTransaction(CreateAllSnapshotsFromVmCommand.java:400)<br>
...<br>
</blockquote>
As a consequence, Engine is showing a failed snapshot as "Current",
while libvirt is still reporting the previous correct snapshot.<br>
I guess next time Engine will probably try to resume the failed
snapshot and VM won't start anymore.<br>
What is the correct way to solve this issue?<br>
<br>
BZ:<br>
<a class="moz-txt-link-freetext"
href="https://bugzilla.redhat.com/show_bug.cgi?id=1018867">h...
</body>
</html>
--------------000701090209060705020903--
11:35 a.m.
New subject: Failed Snapshot as 'Current' after failed Live Storage Migration
----- Original Message -----
From: "Christopher Pereira" <kripper(a)imatronix.cl>
To: devel(a)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.
Thanks, we will look into this.
Nir
7:24 a.m.
On 04-08-2015 5:35, Nir Soffer wrote:
> What is the correct way to solve this issue?
I would restart engine, it may have bad cache.
Thanks Nir,
After restarting Engine, 'Sanpshots' list is still incorrect.
I will continue reporting on BZ [1] to explore if oVirt will be able to
overcome this problems without restarting a VM.
In general, restarting VMs is not possible.
[1] : https://bugzilla.redhat.com/show_bug.cgi?id=1018867
3397
days inactive
3398
days old
2 comments
2 participants
participants (2)
-
Christopher Pereira -
Nir Soffer