Bug 836780

Summary: ovirt-engine-backend: misleading event after successful migration
Product: Red Hat Enterprise Virtualization Manager Reporter: Oded Ramraz <oramraz>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: Barak Dagan <bdagan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: abisogia, acathrow, ahadas, dyasny, iheim, italkohe, lpeer, michal.skrivanek, ofrenkel, pablo.iranzo, pstehlik, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---Keywords: ZStream
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: sf1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 887877 (view as bug list) Environment:
Last Closed: 2013-06-11 08:16:59 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: 887877, 915537    
Attachments:
Description Flags
engine logs none

Description Oded Ramraz 2012-07-01 09:24:49 UTC
Description of problem:
Sometimes after successful migration I see the following event in the events tab: 
"VM oo is down. Exit message: Migration succeeded"
Although it has normal severity it should not appear IMO.  

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Oded Ramraz 2012-07-01 09:27:06 UTC
Created attachment 595511 [details]
engine logs

Comment 2 Michal Skrivanek 2012-07-25 16:22:12 UTC
do not have capacity to fix this in 3.1, seems low prio, proposing defer and/or move to upstream

Comment 8 Arik 2012-11-12 17:53:48 UTC
http://gerrit.ovirt.org/9199

Comment 12 Oded Ramraz 2013-01-30 06:45:19 UTC
Verified sf4

Comment 13 Itamar Heim 2013-06-11 08:16:59 UTC
3.2 has been released

Comment 14 Michal Skrivanek 2014-05-13 08:42:41 UTC
*** Bug 965525 has been marked as a duplicate of this bug. ***