Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-3886:
---------------------------------------------------------------
Summary: VM name on vCenter not getting set correctly when
vm.instancename.flag is set to true
Key: CLOUDSTACK-3886
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3886
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Vmware deployment in cloudstack.
Reporter: Venkata Siva Vijayendra Bhamidipati
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
Fix For: 4.2.0
In a vmware deployment on cloudstack, if the vm.instancename.flag is set to
true, and a displayname is supplied during VM creation, the displayname simply
gets appended to the internal name i-x-y of that VM in vCenter. The expected
behaviour is this:
If the vm.instancename.flag is set to false (default), there is no change in
current behavior:
1. If hostname isn't supplied, it is set to the uuid.
2. If displayname is supplied, it shows up in the GUI. If not, it is set to the
internal VM name i-x-y-VM.
If the vm.instancename.flag is set to true:
1. If hostname is not supplied, and displayname is supplied, set hostname to
displayname, and set the instance name as it appears on vCenter also, to the
displayname.
2. If hostname is not supplied, and displayname is also not supplied, set
hostname to uuid, but set internal name of the VM as it appears on vCenter to
i-x-y-VM as is done currently.
3. If hostname is supplied, set the instance name as it appears on vCenter to
this hostname.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
