[ https://issues.apache.org/jira/browse/CLOUDSTACK-8861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Kumar Anaparti reassigned CLOUDSTACK-8861: ------------------------------------------------- Assignee: Suresh Kumar Anaparti > Cloudstack allows creation of VM's with the same display name when > vm.instancename.flag=true > -------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-8861 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8861 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: Vmware ESXi 5.1 > Reporter: Suresh Kumar Anaparti > Assignee: Suresh Kumar Anaparti > Fix For: 4.6.0 > > > ISSUE > ===== > As per the current design vm.instance.flag behavior has changed. If set to > true, it will only set the "instancename" without any additional prefix. So > if the customer rollouts a instance with the name webserver01, the instance > on the hypervisor will be just webserver01. > However if there is already a VM with name “webserver01” on the hypervisor ( > deployed through Cloudstack) a second account can still create an instance > with the same name. Cloudstack will allow this but on the hypervisor you will > get a instancename already exist error and cloudstack is failing badly in > this situation. > Note: Vmware doesn't support using the same name for VM. > ENVIRONMENT > =========== > [root@ ~]# cloudstack-sccs > f04c81db3841369c0c8357e3cacb5ae790bc8929 > Vmware ESXi 5.1 > STEPS TO REPRODUCE THE ISSUE > ========================== > More easy to reproduce on a cluster with 1 host. > i) Deploy a VM with name say webserver01 from account1 > ii) Now deploy VM with the same name "webserver01" from account2. > During Step ii) you can see that CloudStack will try to create the VM with > the name webserver01, however this fails on the Hypervisor. > EXPECTED BEHAVIOR > ==================== > CloudStack should either throw an error message to user that a VM with the > same name already exists or Should create a VM with some unique name on > VMware. > Note: CloudStack throws an error message when trying to deploy VM with the > same name in the same network, however CloudStack continues with the > deployment if you deploy a VM with the same name in different network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)