vRealize Automation deployment in VMware Cloud Foundation fails with the error "Another VM with same name exists for VRA"
search cancel

vRealize Automation deployment in VMware Cloud Foundation fails with the error "Another VM with same name exists for VRA"

book

Article ID: 316903

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

Symptoms:
  • vRealize Automation deployment in VMware Cloud Foundation fails with the error "Another VM with same name exists for VRA"
  • Not all vRealize Automation Windows VMs have joined Active Directory
  • The problematic VMs that didn't join Active Directory have the first 15 characters from their computer name identically the same.
Example:

LASP-vra01ias01, LASP-vra01ias02, and  LASP-vra01ias03
  • You see messages similar to the following in the /var/log/vmware/vcf/domainmanager/domainmanager.log file located on the SDDC Manager VM:
2019-02-28 01:46:37.463 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] INFO  [      c.v.e.s.c.v.vrlcm.service.VrlcmServiceImpl]   Returned request progress details status = FAILED request ID = f4453537f394cc75582e9341bdb6b
2019-02-28 01:46:37.463 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] INFO  [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   Persisting vRSLCM vRealize operation details in inventory.
2019-02-28 01:46:37.476 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRA deployment failed. vRSLCM Request state is FAILED.
2019-02-28 01:46:37.494 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRSLCM vRealize operation has failed. Error code is VRA_VM_GUEST_TOOLS_NOT_RUNNING.
vRSLCM exception message is Retries exhausted while checking if the VM  LASP-vra01ias01b has joined the domain.
vRSLCM error message is GuestTools not running

2019-02-28 01:47:04.609 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] INFO  [   c.v.e.s.c.client.vmware.vsphere.VcManagerBase]   HA feature on cluster LASP-VRAm01-mgmt01 is true
2019-02-28 01:47:04.612 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] WARN  [c.v.v.v.c.h.i.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase]   Shutting down the connection monitor.
2019-02-28 01:47:04.613 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] ERROR [c.v.e.sddc.orchestrator.model.error.ErrorFactory]   [7TNFU6] VRA_VM_GUEST_TOOLS_NOT_RUNNING GuestTools not running.
com.vmware.evo.sddc.common.vrealize.vrslcm.error.reporting.exceptions.VrslcmOrchTaskException: GuestTools not running.

2019-02-28 01:57:19.141 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] INFO  [      c.v.e.s.c.v.vrlcm.service.VrlcmServiceImpl]   Returned request progress details status = FAILED request ID = f4453537f394cc75582e9341bdb6b
2019-02-28 01:57:19.141 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] INFO  [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   Persisting vRSLCM vRealize operation details in inventory.
2019-02-28 01:57:19.144 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRA deployment failed. vRSLCM Request state is FAILED.
2019-02-28 01:57:19.144 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRSLCM vRealize operation has failed. Error code is VRA_VM_ALREADY_EXISTS.
vRSLCM error message is Another VM with same name exists for VRA

  • You see messages similar to the following in the /var/log/vlcm/vrlcm-server.log file located vRealize Suite Lifecycle Manager VM:
2019-02-28 01:42:21.976 ERROR [pool-2-thread-3] c.v.v.l.p.c.v.t.w.DeployIaasWindowsTemplateTask -  -- Exception while deploying windows template
com.vmware.vrealize.lcm.common.exception.vcenter.GuestToolsNotRunningException: Retries exhausted while checking if the VM  LASP-vra01ias01a has joined the domain

2019-02-28 01:47:30.328 INFO  [pool-2-thread-15] c.v.v.l.d.v.v.u.CoreUtility -  -- VM search name : LASP-vra01ias01a and Cluster is :LASP-VRAm01-mgmt01
2019-02-28 01:47:30.361 INFO  [pool-2-thread-15] c.v.v.l.d.v.v.u.CoreUtility -  -- VM Name  : LASP-vra01ias01a found for cluster: LASP-VRAm01-mgmt01
2019-02-28 01:47:30.361 ERROR [pool-2-thread-15] c.v.v.l.p.c.v.t.w.DeployIaasWindowsTemplateTask -  -- Exception while deploying windows template
com.vmware.vim.binding.vim.fault.DuplicateName: null

2019-02-28 01:47:30.361 INFO  [pool-2-thread-15] c.v.v.l.p.a.s.Task -  -- Injecting task failure event. Error Code : 'LCMVRACONFIG50004', Retry : 'true', Causing Properties : '{ CAUSE :: vmName ===  }'
com.vmware.vim.binding.vim.fault.DuplicateName: null
  • The vRealize Automation VMs that failed to join Domain show Event ID 2505 "Name conflict on the network" in the Event Viewer.
  • The Task Event on the Active Directory Domain Controller will show event ID 5722 . The event will occur When a computer is joined to a domain with a name that already exists.
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Foundation 3.5.x

Cause

This is  expected behavior due to a Microsoft limitation where NetBIOS names can only be 15 characters. For more information see Microsoft support article 909264

Resolution

  1. Login to SDDC Manager UI. Navigate to Administration -> vRealize Suite -> vRealize Automation.
  2. Click the Uninstall button.
  3. Select a different naming convention for the vRealize Automation VMs, where the first 15 characters are not identically the same.
  4. Generate new vRealize Automation Certificates for the  vRealize Automation VMs after changing their computer names.
  5. Initiate a new vRealize Automation deployment.


Powered by Wolken Software