[
https://issues.apache.org/jira/browse/CLOUDSTACK-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland updated CLOUDSTACK-8112:
--------------------------------------
Fix Version/s: (was: Future)
4.4.3
> 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: 4.4.3
>
>
> 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)
