Description of problem: until http://gerrit.ovirt.org/#/c/27465/ , VDSM had a bug which caused incorrect migration progress to be reported. This is caused by migration slow to start for whatever reason; in this scenario VDSM will mistakely report libvirt data for 100% migration completed, but once real data is available, the progress will jump back to lower values. Besides the UI inconsistency, this may be misinterpreted for migration stalling, and may in turn cause unwanted migration cancellation. Version-Release number of selected component (if applicable): 3.4.x How reproducible: Not easy. Initial phase of migration must stall for whatever reason. Steps to Reproduce: 1. Have migration start slowly, for example by having slow DNS 2. See migration mistakenly reported as 100% completed, than observe real progress value 3. Actual results: Actually depending on the interleave of the events, migration can be cancelled Expected results: correct progress, no unwanted cancelation Additional info: The scenario, although unlikely, is not hypotetical but observed in https://bugzilla.redhat.com/show_bug.cgi?id=1104073
This is an automated message oVirt 3.4.3 has been released: * should fix your issue * should be available at your local mirror within two days. If problems still persist, please make note of it in this bug report.