Bug 1294500 - v2v: Cannot import VM as clone if the VM was already imported (not as clone).
Summary: v2v: Cannot import VM as clone if the VM was already imported (not as clone).
Keywords:
Status: CLOSED DUPLICATE of bug 1294501
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: Nisim Simsolo
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-28 14:39 UTC by Nisim Simsolo
Modified: 2015-12-28 14:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-28 14:49:46 UTC
oVirt Team: ---
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Nisim Simsolo 2015-12-28 14:39:55 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:49:46 UTC

*** This bug has been marked as a duplicate of bug 1294501 ***


Note You need to log in before you can comment on or make changes to this bug.