+++ This bug is a downstream clone. The original bug is: +++
+++ bug 1497355 +++
Description of problem:
The snapshot creation of a Live Storage Migration hung and timed out on the engine side. However, the engine then continued on with CloneImageGroupStructureVDSCommand and VmReplicateDiskStartVDSCommand, etc.
The result was that the LSM effectively failed, with the disk still residing in the source storage domain. However, volumes were created in the target storage domain, which caused a subsequent LSM to fail.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(Originally by Gordon Watson)
Benny, can you take a look please?
Tentitively targetting for 4.2.
If there's something safe enough to backport to 4.1.z, we should do that, but I'm not commiting on such a fix unless we see what the upstream fix contains.
(Originally by amureini)
Live storage migration is aborted in case of a snapshot creation failure:
2018-06-19 16:34:28,149+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-62)  EVENT_ID: USER_CREATE_SNAPSHOT_FINISHED_FAILURE(69),
Failed to complete snapshot 'test1_Disk1 Auto-generated for Live Storage Migration' creation for VM 'test1'.
2018-06-19 16:34:30,249+03 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-42) [56a5561c-14dd-4b09-ad90-5f23f20c40ca] Ending command 'org.ovir
t.engine.core.bll.storage.lsm.LiveMigrateDiskCommand' with failure.
*** Bug 1591514 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.