Bug 1366990
Summary: | Import from Xen and KVM: import dilaog - VM should not be checked as "clone" when there is identical VM name in a different DC. | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Nisim Simsolo <nsimsolo> | ||||||||||||||
Component: | BLL.Virt | Assignee: | Sharon Gratch <sgratch> | ||||||||||||||
Status: | CLOSED NOTABUG | QA Contact: | Nisim Simsolo <nsimsolo> | ||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||
Priority: | medium | ||||||||||||||||
Version: | 4.0.2.6 | CC: | bugs, mgoldboi, nsimsolo, tjelinek | ||||||||||||||
Target Milestone: | ovirt-4.0.6 | Flags: | tjelinek:
ovirt-4.0.z?
mgoldboi: planning_ack+ rule-engine: devel_ack? mavital: testing_ack+ |
||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2016-11-02 13:51:27 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: | |||||||||||||||||
Attachments: |
|
Description
Nisim Simsolo
2016-08-15 08:17:29 UTC
Created attachment 1190809 [details]
vdsm.log
Created attachment 1190810 [details]
engine.log
Created attachment 1190811 [details]
first import dialog
Created attachment 1190812 [details]
second_import_dialog
Created attachment 1190813 [details]
VMware second import dialog (clone is unchecked)
Created attachment 1190814 [details]
KVM second import dialog (clone is checked)
It is not a bug. Details: A VM is marked as clone only if there is another vm in the system that has the SAME id, regardless to the data center it belongs to. The VM is is unique cross DCs. So for XEN and KVM it work as expected in the attached tests because trying to import a VM that is already existed with the same id in the system (under other data center) should mark the VM as cloned. For VMware it should work the same and it does. The reason it wasn't marked as clone in the attached test is that the existed VM had an id started with fb0f..... and the imported VM had an id started with 423c8...so those are 2 different VMS with the same name (see "VMware_second_dialog" attachment). to summarize there are 2 scenarios: 1) import a VM with the same id as one existed in the system -> in this case the VM is marked to be imported as clone. 2) import a VM with the same name as other VM existed under a different dc, but with a different id -> in this case it will be imported as is (not marked as clone) |