Bug 1427566

Summary: Migration downtime not displayed
Product: [oVirt] ovirt-engine Reporter: Milan Zamazal <mzamazal>
Component: Backend.CoreAssignee: Shmuel Melamud <smelamud>
Status: CLOSED CURRENTRELEASE QA Contact: Israel Pinto <ipinto>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, lveyde, michal.skrivanek
Target Milestone: ovirt-4.1.2Keywords: Regression
Target Release: 4.1.2Flags: rule-engine: ovirt-4.1+
rule-engine: blocker+
michal.skrivanek: testing_plan_complete?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-23 08:20:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Zamazal 2017-02-28 15:46:05 UTC 
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.
Comment 1 Red Hat Bugzilla Rules Engine 2017-03-21 12:43:09 UTC 
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.
Comment 2 Milan Zamazal 2017-03-29 07:12:52 UTC 
Backport of the Vdsm patch is missing.
Comment 3 rhev-integ 2017-04-26 10:11:40 UTC 
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
Comment 4 Israel Pinto 2017-05-03 11:34:11 UTC 
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