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.
Created attachment 970419 [details] VDSM log from SPM Host 1
Created attachment 970420 [details] VDSM log from SPM Host 2
Created attachment 970421 [details] oVirt Engine Log
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).
Did you try to import with the clone flag marked?
I just tried with the clone flag marked and it failed as well.
Created attachment 974727 [details] oVirt Engine Log - Failed Cloned Import
Created attachment 974728 [details] VDSM log from SPM Host - Failed Cloned Import
I have attached the logs from the failed import using clone flag.
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.
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.
Setting back to NEEDINFO. See the request in comment 10.
After upgrading oVirt to 3.5.1 and performing yum upgrade on the ovirt hosts I was able to import the VM successfully.
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