Bug 965525 - Inaccurate message displayed after VM live migration finishes
Inaccurate message displayed after VM live migration finishes
Status: CLOSED DUPLICATE of bug 836780
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.5.0
Assigned To: Shahar Havivi
Tareq Alayan
: 970928 (view as bug list)
Depends On:
Blocks: rhev3.5beta 1156165
  Show dependency treegraph
Reported: 2013-05-21 06:28 EDT by Alexander Bisogiannis
Modified: 2015-09-22 09 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-13 04:42:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexander Bisogiannis 2013-05-21 06:28:34 EDT
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:

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 10:14:31 EDT
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 07:34:03 EDT
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 02:32:51 EDT
*** Bug 970928 has been marked as a duplicate of this bug. ***
Comment 5 Shahar Havivi 2013-10-27 09:26:36 EDT
Does the message is error message or a regular event log?
Comment 7 Michal Skrivanek 2014-04-01 05:06:39 EDT
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 04:42:41 EDT

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

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