vRealize product deployment in VMware Cloud Foundation fails while deploying one of the virtual machines
book
Article ID: 316762
calendar_today
Updated On:
Products
VMware Cloud Foundation
Issue/Introduction
Symptoms:
vRealize product deployment (vRealize Automation, vRealize Operations, vRealize Suite Lifecycle Manager) in VMware Cloud Foundation fails while deploying one of the virtual machines
There is already a virtual machine present in the vSphere inventory with the same name as one of the vRealize virtual machines being deployed
Cause
During the deployment of a vRealize product, the fully qualified domain name (FQDN) is specified by the user and the virtual machine is created in vCenter Server with the short version of the FQDN. The process for deploying vRealize products in VMware Cloud Foundation does not pre-validate that there are no naming conflicts with virtual machines already in the vSphere inventory.
Resolution
This is a known issue affecting VMware Cloud Foundation. There is currently no resolution.
Workaround: To workaround this issue, ensure that there are no virtual machines present in the vSphere inventory that will produce a naming conflict with the virtual machine names specified for the vRealize product deployment prior to starting.
If the vRealize Automation deployment fails due to this issue, one of the two following options can be used:
Click the Uninstall button on the Administration->vRealize Suite-><vRealize product>Â page and attempt the deployment again with non-conflicting virtual machine names.
Rename the existing VMs that are causing the naming conflict. Click the Retry button next to the failed deployment task in the SDDC Manager UI.