[
https://issues.apache.org/jira/browse/CLOUDSTACK-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Likitha Shetty updated CLOUDSTACK-7150:
---------------------------------------
Description:
When global config 'vm.instancename' is set to true, VM name in vCenter is not
being constructed correctly. The name in vCenter should be
'<instance_name>-<vm_hostname>'.
For e.g. for a VM with CS internal name i-2-3-VM is named in vCenter as
i-2-<hostname> whereas it should be i-2-3-<hostname>.
was:
When global config 'vm.instancename' is set to true, VM name on vCenter is not
being constructed correctly. The name on vCenter should be
'<instance_name>-<vm_hostname>'.
For e.g. for a VM with CS internal name i-2-3-VM is named on vCenter as
i-2-<hostname> whereas it should be i-2-3-<hostname>.
> [VMware] Global config 'vm.instancename' is not honored
> -------------------------------------------------------
>
> Key: CLOUDSTACK-7150
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7150
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.5.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Fix For: 4.5.0
>
>
> When global config 'vm.instancename' is set to true, VM name in vCenter is
> not being constructed correctly. The name in vCenter should be
> '<instance_name>-<vm_hostname>'.
> For e.g. for a VM with CS internal name i-2-3-VM is named in vCenter as
> i-2-<hostname> whereas it should be i-2-3-<hostname>.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
