Bug 1427566 - Migration downtime not displayed
Summary: Migration downtime not displayed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Shmuel Melamud
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-28 15:46 UTC by Milan Zamazal
Modified: 2017-05-23 08:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:20:53 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+
michal.skrivanek: testing_plan_complete?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 74483 0 master MERGED virt: Add artificial delay after migration on destination 2017-03-28 18:11:37 UTC
oVirt gerrit 74515 0 master MERGED core: Get migration downtime from event 2017-03-23 11:23:17 UTC
oVirt gerrit 74705 0 ovirt-engine-4.1 MERGED core: Get migration downtime from event 2017-03-28 16:47:08 UTC
oVirt gerrit 74790 0 ovirt-4.1 MERGED virt: Add artificial delay after migration on destination 2017-03-29 10:17:00 UTC

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


Note You need to log in before you can comment on or make changes to this bug.