Thanks for the info, I will be sure to update to 4.2.2 when it is ready.
With out the ability to migrate vm's based on this image it makes it less
convenient to patch my servers on a more consistent basis.I was also
experiencing this issue prior to upgrading my environment to 4.2.
From: "Milan Zamazal (mzamazal(a)redhat.com)" <mzamazal(a)redhat.com>
To: "Bryan Sockel" <Bryan.Sockel(a)mdaemon.com>
Cc: "users\(a)ovirt.org" <users(a)ovirt.org>
Date: Thu, 01 Mar 2018 17:38:24 +0100
Subject: Re: VM Migrations
"Bryan Sockel" <Bryan.Sockel(a)mdaemon.com> writes:
I am having an issue migrating all vm's based on a specific
template was created in a previous ovirt environment (4.1), and all VM's
deployed from this template experience the same issue.
I would like to find a resolution to both the template and vm's that are
already deployed from this template. The VM in question is VDI-Bryan and
the migration starts around 12:25. I have attached the engine.log and the
vdsm.log file from the destination server.
The VM died on the destination before it could be migrated and I can't
see the exact reason in the log. However I can see there that you have
been hit by some 4.1->4.2 migration issues and it's likely to be the
problem as well as being a problem by itself in any case.
That will be fixed in 4.2.2. If you don't want to wait until 4.2.2 is
released, you may want to try current 4.2.2 snapshot, which already
contains the fixes.