[
https://issues.apache.org/jira/browse/CLOUDSTACK-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256740#comment-14256740
]
ASF subversion and git services commented on CLOUDSTACK-8112:
-------------------------------------------------------------
Commit 5f9e4fddf303f312a0b17abc0d837f28042caeda in cloudstack's branch
refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5f9e4fd ]
CLOUDSTACK-8112. CS allows creation of VM's with the same Display name when
vm.instancename.flag is set to true.
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.
> 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)
