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