Bug 965525

Summary: Inaccurate message displayed after VM live migration finishes
Product: Red Hat Enterprise Virtualization Manager Reporter: Alexander Bisogiannis <abisogia>
Component: vdsmAssignee: Shahar Havivi <shavivi>
Status: CLOSED DUPLICATE QA Contact: Tareq Alayan <talayan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: abisogia, acathrow, aglotov, bazulay, hkim, iheim, jkt, lpeer, lyarwood, michal.skrivanek, pstehlik, Rhev-m-bugs, sputhenp, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-13 08:42:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1142923, 1156165    

Description Alexander Bisogiannis 2013-05-21 10:28:34 UTC
Description of problem:
Upon live migration of a VM, the Event log reports

"VM <vm_name> is down. Exit Message: Migration succeeded"


Version-Release number of selected component (if applicable):

RHEVM 3.1.0-50

How reproducible:
Live migrating any VM gives the same message. Appears to be move prevalent when live-migrating multiple VM concurrently, for instance when placing a loaded hypervisor into maintenance mode.

Steps to Reproduce:
1.
2.
3.

Actual results:

Confusing message appears, probably from source host reporting that the VM is down.

Expected results:

The message should note if the migration succeeded or not, not from the source host saying that the VM is down.

Additional info:


The message comes from the source host reporting that he VM is down, which is technically correct, but irrelevant.

Comment 1 Michal Skrivanek 2013-05-22 14:14:31 UTC
there seems to be a race in setDownStatus, it first set status to Down and only after that actually stop the statistics thread. If you're unlucky the stats get sent in the meantime

vdsm logs would help to confirm

Comment 2 Martin Polednik 2013-09-11 11:34:03 UTC
After investigation, we've agreed on moving this bug to engine, as from vdsm's point of view the status of migrated VM is simply poweroff/nonexistant and no further information should be sent. Engine should supress the message and focus on success of migration on destination host.

Comment 3 Michal Skrivanek 2013-09-17 06:32:51 UTC
*** Bug 970928 has been marked as a duplicate of this bug. ***

Comment 5 Shahar Havivi 2013-10-27 13:26:36 UTC
Does the message is error message or a regular event log?

Comment 7 Michal Skrivanek 2014-04-01 09:06:39 UTC
we want to suppress this to not alarm users…it's a normal case and you get the migration succeeded event afterwards anyway

Comment 12 Michal Skrivanek 2014-05-13 08:42:41 UTC

*** This bug has been marked as a duplicate of bug 836780 ***