Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1175599

Summary: Import of a v2v-ed VM from Export Domain Fails
Product: [Retired] oVirt Reporter: Sokratis <sokratis123k>
Component: ovirt-engine-webadminAssignee: Tal Nisan <tnisan>
Status: CLOSED WORKSFORME QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5CC: ahadas, amureini, bugs, ecohen, gklein, iheim, lsurette, mgoldboi, rbalakri, redhat-bugzilla, rjones, sokratis123k, tnisan, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-26 12:12:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1193195    
Attachments:
Description Flags
VDSM log from SPM Host 1
none
VDSM log from SPM Host 2
none
oVirt Engine Log
none
oVirt Engine Log - Failed Cloned Import
none
VDSM log from SPM Host - Failed Cloned Import none

Description Sokratis 2014-12-18 07:31:19 UTC 
Description of problem:

After converting an Oracle Linux VMware VM and trying to import it from the oVirt Export domain to an FC Data Domain the import fails. 

When tried for the second time the import didn't proceed and the following error was thrown:

cannot import vm. the storage domain already contains the target disk(s).



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


How reproducible:


Steps to Reproduce:
1. Import VM from Export Domain
2.
3.

Actual results:

Import fails

Expected results:

Import completes successfully

Additional info:

I had the same problem on two different data domains.
Comment 1 Sokratis 2014-12-18 07:33:55 UTC 
Created attachment 970419 [details]
VDSM log from SPM Host 1
Comment 2 Sokratis 2014-12-18 07:34:19 UTC 
Created attachment 970420 [details]
VDSM log from SPM Host 2
Comment 3 Sokratis 2014-12-18 07:34:44 UTC 
Created attachment 970421 [details]
oVirt Engine Log
Comment 4 Sokratis 2014-12-18 07:35:37 UTC 
I have also attached the vdsm log from the SPM Host as well as the engine log at the time of the failure (yesterday 17/12/2014 around 16:00).
Comment 5 Tal Nisan 2014-12-21 10:44:09 UTC 
Did you try to import with the clone flag marked?
Comment 6 Sokratis 2014-12-31 08:51:40 UTC 
I just tried with the clone flag marked and it failed as well.
Comment 7 Sokratis 2014-12-31 09:07:28 UTC 
Created attachment 974727 [details]
oVirt Engine Log - Failed Cloned Import
Comment 8 Sokratis 2014-12-31 09:07:52 UTC 
Created attachment 974728 [details]
VDSM log from SPM Host - Failed Cloned Import
Comment 9 Sokratis 2014-12-31 09:08:15 UTC 
I have attached the logs from the failed import using clone flag.
Comment 10 Richard W.M. Jones 2015-01-19 08:12:45 UTC 
I'm fairly sure the clone flag is nothing to do with this.

The problem is I have no idea what the name/UUID/anything
else about the VM is that you tried to import, so all I have
is a couple of vast log files with no idea what to look for.

Please try to extract the real error from the SPM host logs.

Tal: It would greatly help if oVirt reflected the real
underlying error in all error messages which are presented
to the user.  The current situation is ridiculous.
Comment 11 Sokratis 2015-01-19 10:58:51 UTC 
What I have noticed is that the import fails only with VMs that have been converted from VMware using the latest virt-v2v (on CentOS 7). 

I have tried this with two different VMs and I have the same problem.

Then I performed a couple of conversions using the old virt-v2v (CentOS 6) and I was able to import the VMs successfully.
Comment 12 Richard W.M. Jones 2015-01-19 14:23:35 UTC 
Setting back to NEEDINFO.  See the request in comment 10.
Comment 13 Sokratis 2015-01-26 12:04:39 UTC 
After upgrading oVirt to 3.5.1 and performing yum upgrade on the ovirt hosts I was able to import the VM successfully.
Comment 14 Tal Nisan 2015-01-26 12:12:46 UTC 
Given comment 13 closing the bug.
Richard, you can open a specific bug on the error about the info you'd like to see in the log so we can discuss and change it if possible and necessary