| 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.Virt | Assignee: | Michal Skrivanek <michal.skrivanek> |
| Status: | CLOSED DUPLICATE | QA Contact: | Nisim Simsolo <nsimsolo> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.1 | CC: | bugs, nsimsolo |
| Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-28 14:49:46 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: | |
*** This bug has been marked as a duplicate of bug 1294501 *** |
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