VCF 9.0 Deployment fails at installing VCF Automation with error "Not all ESXi Hosts in the cluster <cluster-name> are connected to the datastore <datastore> nERR:INIT0001 - Validating configuration\n","exceptionStackTrace":
search cancel

VCF 9.0 Deployment fails at installing VCF Automation with error "Not all ESXi Hosts in the cluster <cluster-name> are connected to the datastore <datastore> nERR:INIT0001 - Validating configuration\n","exceptionStackTrace":

book

Article ID: 421541

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • New VCF deployment fails at the stage where the Installer is trying to setup a new VCF Automation Appliance.

  • Below error is associated with the failed task to deploy VCF Automation Appliance.

    Request createenvironment failed with error cause [{"messageId":"LCMVSPHERECONFIG1000095","message":"LCMVSPHERECONFIG1000095","eventId":"<ID>","retry":true,"exceptionMessage":"Failed to create services platform cluster. Refer to /var/log/vrlcm/vmsp_bootstrap_xxxxx.log for more details. <Date and time> 6 role VCF Services Platform exists\n<Date and time> role VCF Services Platform Admin exists\nsuccessfully added global permissions for user <svc-ID>@<domain>\nsuccessfully added global permissions for user svc-<ID>@<domain>\n<Date and time> ERROR : Not all ESXi Hosts in the cluster <cluster> are connected to the datastore <datastore>.\nERR:INIT0001 - Validating configuration\n","exceptionStackTrace":"java.lang.Exception: Failed to create services platform cluster. Refer to /var/log/vrlcm/vmsp_bootstrap_xxxxx.log for more details. <Date and time> role VCF Services Platform exists\n<Date and time> role VCF Services Platform Admin exists\nsuccessfully added global permissions for user svc-<ID>@<domain>\nsuccessfully added global permissions for user svc-<ID>@<domain>\n<Date and time> ERROR : Not all ESXi Hosts in the cluster <cluster> are connected to the datastore<datastore>.\nERR:INIT0001 - Validating configuration\n\n\tat 

Environment

VMware Cloud Foundation 9.x

Cause

The issue occurs because the VCF installer uses the same datastore where vCenter is deployed to deploy the VCF Management components, including VCF Automation. If the vCenter is deployed on a local datastore (local-DS) instead of a shared datastore, the installer attempts to deploy VCF Automation appliance too on the local Datastore which leads to this failure.

Resolution

This issue shall be addressed in one of the future releases.

Follow the below workaround to complete the VCF Automation deployment.

  1. Log in to VCF Operations.
  2. Navigate to Fleet Management → Lifecycle.
  3. Go to the Task section. 
  4. Under Tasks, click on the value "Failed" under "Request Status".
  5. Select Retry to view all the fields available for update.
  6. Update the **Datastore** field with a valid value in the format. For example- `Datastore:datastore-13`, where `datastore-13` is the MoRef ID of the datastore. 
  7. Click "Submit" to apply the changes.

    To obtain the MoRefID of the Datastore, on the vSphere Client under the "Datastore" section click on the required datastore object. Go to the Address bar and in the URL, look for the value "datastore-<ID>". The "datastore-<ID>" is the MoRefID here.