[
https://issues.apache.org/jira/browse/CLOUDSTACK-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Likitha Shetty resolved CLOUDSTACK-8112.
----------------------------------------
Resolution: Fixed
During VM creation, if vm.instancename.flag is set to true and hypervisor type
is VMware, check if VM with the same hostname already exists in the zone.
Why is check being made under the zone?
There are two types of VMware zones: legacy zones and non-legacy zones.
- In case of a non-legacy zone, since a CS zone maps to a VMware DC, by
checking under the CS zone we ensure that no two VMs with same name are created
under the same DC.
- In case of legacy zone, we don't have 1-1 mapping between CS zones and VMware
DCs. But we still need to check under the entire zone to avoid any potential
failures for other CS operations. For e.g. In case of cold migration, CS allows
a volume to be moved across between VMware DCs if they belong to the same CS
zone. Now if a VM with an existing VM name is allowed to be created under a
different DC (but same CS zone) the after a cold migration, when an attempt is
made to start the VM it will fail with conflicting name issue.
> Creating VM using an existing display name fails when vm.instancename.flag is
> set to true.
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8112
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8112
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Fix For: Future
>
>
> CS restricts 2 VMs from having the same name only if they are in the same
> network. But in case vm.instancename.flag is set to true, VM name in vCenter
> will be its VM's CS display name. And vCenter doesn't allow two VMs to have
> the same name under the same DC which results in the failure of VM start in
> CS and is not handled correctly.
> CS should throw an error message to the user that a VM with the same name
> already exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
