rstoker13
VMware Employee
VMware Employee

Azure XaaS doesn't appear to allocate hostnames properly

When provisioning machines via the Azure plugin(Built-in XaaS) we have noticed that it assigns a hostname according to the machine prefix and will increment based on existing VMs within Azure, but does not increment the Machine Prefix number. Therefore the next VM deployed to vCenter, takes the name of a machine that has already been provisioned to Azure. Has anyone experienced this? Any suggestions for a resolution? I will open a support case if necessary.

pastedImage_0.png

pastedImage_1.png

0 Kudos
2 Replies
daphnissov
Immortal
Immortal

This is interesting to know about. Are you using 7.3? If this is a confirmed issue, the only workaround may be to use a different naming scheme for Azure. Please update the thread with whatever you hear from support.

0 Kudos
rstoker13
VMware Employee
VMware Employee

We are using 7.3. A different naming scheme may circumvent the issue, but bypasses our enterprise standards for naming. Also, it still would be unable to increment the naming prefix in vRA, which means it would only increment based on what Azure VMs currently exist. This process is very quick in a small environment, but if we reach hundreds of VMs, the process will likely become much slower.

We have a ticket opened and as soon as we receive resolution, I will update this thread. Thanks.

0 Kudos