Description of problem: When I successfully migrate a VM, VM downtime is displayed as unavailable in messages. "Migration completed" message says "Actual downtime: (N/A)". Version-Release number of selected component (if applicable): oVirt master oVirt 4.1 How reproducible: Always. Steps to Reproduce: 1. Migrate a VM. 2. Look at "Migration completed" message in "Events" tab of the VM after the migration is finished. Actual results: The message contains "Actual downtime: (N/A)". Expected results: The message contains something like "Actual downtime: 230 ms." Additional info: Engine should consume "|virt|VM_migration_status|" event that contains the downtime information and information whether the migration finished in pre-copy or post-copy mode. Please note that the meaning of the value differs for pre-copy and post-copy migrations. While for pre-copy migrations it's actual measured downtime, for post-copy migrations it's just a computed downtime including control flow transfer. You may or may not want to distinguish that difference in the message.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Backport of the Vdsm patch is missing.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [PROJECT 'vdsm'/PRODUCT 'ovirt-engine' MISMATCH] For more info please contact: infra
Verify with: Steps: 1. Create VMs with different memory size 2. Migrate VMs 3. Check 'Actual downtime' Results: In all the migration the 'Actual downtime' is shown