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

Bug 1294501

Summary: v2v: Cannot import VM as clone if the VM was already imported (not as clone).
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.1CC: ahadas, bugs, mavital, michal.skrivanek, nsimsolo, sbonazzo
Target Milestone: ovirt-3.6.3Flags: rule-engine: ovirt-3.6.z+
rule-engine: planning_ack+
michal.skrivanek: devel_ack+
mavital: testing_ack+
Target Release: 3.6.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:02:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1294651    
Bug Blocks: 952703, 1236075    
Attachments:
Description Flags
engine.log
none
vdsm.log
none
webadmin screenshot none

Description Nisim Simsolo 2015-12-28 14:41:26 UTC
Description of problem:
Importing VM as clone when the same VM was already imported, failed with "VM Id already exist in the system" error message.
This issue is true also when changing destination VM name.

Version-Release number of selected component (if applicable):
rhevm-3.6.2-0.1.el6
vdsm-4.17.14-0.el7ev.noarch
sanlock-3.2.4-1.el7.x86_64
libvirt-client-1.2.17-13.el7_2.2.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.4.x86_64

How reproducible:
Consistently.

Steps to Reproduce:
1. Import VM from VMware, not as a clone.
2. Import the same VM again, verify clone checkbox is checked, change VM name and click "ok".
3.

Actual results:
Action failed with the next message: 
Error while executing action:

test888:

    Import VM failed - VM Id already exist in the system. Please remove the VM (rhel7_nisim) from the system first

Expected results:
Import VM as clone should succeed.

Additional info:
engine and vdsm log attached.
Engine.log issue: 2015-12-28 16:35:36,283 INFO

Comment 1 Nisim Simsolo 2015-12-28 14:44:00 UTC
Created attachment 1110034 [details]
engine.log

Comment 2 Nisim Simsolo 2015-12-28 14:44:31 UTC
Created attachment 1110035 [details]
vdsm.log

Comment 3 Nisim Simsolo 2015-12-28 14:45:54 UTC
Created attachment 1110036 [details]
webadmin screenshot

Comment 4 Nisim Simsolo 2015-12-28 14:49:46 UTC
*** Bug 1294500 has been marked as a duplicate of this bug. ***

Comment 5 meital avital 2016-02-08 16:50:17 UTC
Verified on :
rhevm-3.6.3-0.1.el6
libvirt-client-1.2.17-13.el7_2.2.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.4.x86_64
vdsm-4.17.19-0.el7ev.noarch

Verified steps:
1)Import VM1 from VMware, not as a clone.
2)Import the same VM1 again as clone, changed VM name.
3)Import the same VM1 again as clone, with name that match other VM in VMware.
4)Import VM2 in the first time and check the clone checkbox.