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 VMware Cloud Foundation 9.x
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.
This issue shall be addressed in one of the future releases.
Follow the below workaround to complete the VCF Automation deployment.