As part of migration monitoring, we should show error messages that occur on the destination host before the handoff phase. As part of the fix for bz 1104195, we removed such audit logs because they were confusing and were not shown properly. We probably need vdsm on the source host to fetch the error message, if exists, on the destination host so we will be able to query that from the engine using the migrate-status command. Then, it could be nice to present summary of the migration: tried from host A to B, exit status (from the dest host): <..> ... succeeded to migrate to host Z And to show the duration of the whole process as well.
Francesco, getting the dst side logs is probably a good idea
This seems specular to what we have in https://bugzilla.redhat.com/show_bug.cgi?id=1154397 I think we can merge the two issues since it seems there are actually one: we should centralize the information about migration failures and make easy for Engine to understand what's happening/happened without losing information. On https://bugzilla.redhat.com/show_bug.cgi?id=1154397 I added a patch to propagate abort reason to destination. After a quick read of this BZ, it seems that we actually need also the other way around.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Any update to this bug? Is it being worked on for 4.0?
We require changes on both Engine and Vdsm to properly fix this. We are discussing the issue internally on the virt team but no final patch(es) yet.
postponing to 4.1 due to capacity.
I think this was solved by monitoring and migration changes introduced in 4.1.0 (postcopy et. al.) Please reopen if it still happens.
Worth further consideration (with no prio increase) after http://lists.ovirt.org/pipermail/users/2016-December/044477.html
doc_text not required; this error was just misleading, and now is gone. Patches merged in the ovirt-4.1 branch -> MODIFIED
(In reply to Francesco Romani from comment #10) > doc_text not required; this error was just misleading, and now is gone. > Patches merged in the ovirt-4.1 branch -> MODIFIED The fix was done on the Vdsm side.
Verify with: Engine: 4.1.1.3-0.1.el7 Host: OS Version:RHEL - 7.3 - 7.el7 Kernel Version:3.10.0 - 550.el7.x86_64 KVM Version:2.6.0 - 28.el7_3.3.1 LIBVIRT Version:libvirt-2.0.0-10.el7_3.5 VDSM Version:vdsm-4.19.7-1.el7ev SPICE Version:0.12.4 - 20.el7_3 Steps: Migrate vm with load and make the migration failed, check the the error massage: 'Domain not found: no domain with matching uuid' don't exists.