[
https://issues.apache.org/jira/browse/CLOUDSTACK-8637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627832#comment-14627832
]
ASF GitHub Bot commented on CLOUDSTACK-8637:
--------------------------------------------
GitHub user pritisarap12 opened a pull request:
https://github.com/apache/cloudstack/pull/594
CLOUDSTACK-8637: Verify that VM with same Display name creation fails if
vm.instancename.flag=true
When vm.instancename.flag=true it will only set the "instancename" without
any additional prefix so name of the instance on host will also be same hence
verify that when tried to create another instance with same name on same host
should fail on VMWare as it should have every instance with unique name.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pritisarap12/cloudstack
CLOUDSTACK-8637-Verify-that-cloudstack-gives-error-on-creation-of-VMs-with-the-same-Display-name-when-vm.instancename.flag=true
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/594.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #594
----
commit a2df28d2f7f2596a121a53ee064250b62bb3b6c2
Author: Priti Sarap <[email protected]>
Date: 2015-07-15T09:46:24Z
CLOUDSTACK-8637: Verify that VM with same Display name creation fails if
vm.instancename.flag=true
----
> Verify that cloudstack gives error on creation of VM's with the same Display
> name when vm.instancename.flag=true
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8637
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8637
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Affects Versions: 4.2.1
> Reporter: Priti Sarap
> Fix For: 4.2.1
>
>
> When vm.instancename.flag=true it will only set the "instancename" without
> any additional prefix so name of the instance on hypervisor will also be same
> hence verify that when tried to create another instance with same name on
> same hypervisor should fail on VMWare as it should have every instance with
> unique name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)