Bug 905442

Summary: ovirt-engine-backend: Migration fails with Destination:UNKNOWN error message
Product: Red Hat Enterprise Virtualization Manager Reporter: Oded Ramraz <oramraz>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, ahadas, dyasny, iheim, lpeer, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---Keywords: Regression
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 13:46:02 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:
Attachments:
Description Flags
engine and vdsm logs none

Description Oded Ramraz 2013-01-29 13:15:33 UTC 
Description of problem:

When I try to migrate multiple VM's simultaneously few of the migration operations fails with "Migration failed (Vm:X , Source:Y , destination:UNKNOWN)" error message . 
Attached engine / vdsm logs 
 

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 2013-01-29 13:20:25 UTC 
Created attachment 689830 [details]
engine and vdsm logs
Comment 3 Arik 2013-02-03 15:59:50 UTC 
I managed to migrate multiple VMs (6 VMs) simultaneously from the UI couple of times without a problem

I tried to figure out the use case in which the migrations failed from the attached logs - I see that few migrations failed in 28-1-2013 between 16:58:44-17:00:50, but it's not easy to understand what was going-on there (did you switched to maintenance the destination host in the first time the migration failed?)..

Oded, I need more information about the configuration of the environment (how many hosts, are they all ok..) and what are the steps to reproduce the problem, could you please add it?
Comment 4 Oded Ramraz 2013-02-21 13:46:02 UTC 
I didn't managed to reproduce this issue for a while , closing this bug for now .