VCF 9.0 deployment stuck at "Retrieve the status of VCF Automation Deployment request" with error "Unable to get request status for request <ID> Reference Token: <Token-ID> The Primary Virtual IP Address is already in use./nERR:INIT "

Products

• VMware Cloud Foundation

Issue/Introduction

• A new VCF deployment gets stuck when deploying VCF Automation Appliance.
  
  
• Below is the error that is seen in the Installer Appliance UI.
  
  
  java.lang.Exception: Failed to create services platform cluster. Refer to /var/log/vrlcm/vmsp_bootstrap_xxxxx.log for more details. YYYY/MM/DD HH:MM:SS role VCF Services Platform exists
  YYYY/MM/DD HH:MM:SS role VCF Services Platform Admin exists
  successfully added global permissions for user <User-ID>@vsphere.gen.lab
  successfully added global permissions for user <User-ID>@vsphere.gen.lab
  YYYY/MM/DD HH:MM:SS ERROR : The Primary Virtual IP Address <IP Address> is already in use.
  ERR:INIT0001 - Validating configuration
   
  at com.vmware.vrealize.lcm.vmsp.plugin.tasks.BootstrapVMSPTask.execute(BootstrapVMSPTask.java:108)
  at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158)
  at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  at java.base/java.lang.Thread.run(Unknown Source)

 

Environment

VMware Cloud Foundation 9.x

Cause

An IP conflict in the environment is causing the VCF Automation deployment to bottleneck. This can also occur if some stale Virtual Machines are still present in the setup which were created as a result of the failed VCF Automation deployment workflow and weren't cleaned up.

Resolution

Use a different IP range to provision VCF Automation Appliances.

or

Power OFF the stale Virtual Machines which have the IP Addresses still assigned to them.