Bug 836780 - ovirt-engine-backend: misleading event after successful migration
Summary: ovirt-engine-backend: misleading event after successful migration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.2.0
Assignee: Arik
QA Contact: Barak Dagan
URL:
Whiteboard: virt
: 965525 (view as bug list)
Depends On:
Blocks: 887877 915537
TreeView+ depends on / blocked
 
Reported: 2012-07-01 09:24 UTC by Oded Ramraz
Modified: 2014-07-13 23:18 UTC (History)
14 users (show)

Fixed In Version: sf1
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 887877 (view as bug list)
Environment:
Last Closed: 2013-06-11 08:16:59 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
engine logs (55.54 KB, application/zip)
2012-07-01 09:27 UTC, Oded Ramraz 		no flags Details
View All

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 11 Arik 2012-12-20 15:21:32 UTC 
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=6f48221827f308a03b1b21209e7dc37be30e210b
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. ***
Note You need to log in before you can comment on or make changes to this bug.