VCF Services Platform Cluster Creation Fails during Automation Appliance Deployment | VCF Management Services cluster bootstrap failed

Products

• VCF Automation
• VCF Operations
• VMware Cloud Foundation

Issue/Introduction

• During a migration from a standard vSphere environment to VMware Cloud Foundation (VCF) 9.0 or a Greenfield deployment of VCF 9.0/9.1, the deployment and configuration of the Automation Appliance fails.
  
  Error Code: LCMVSPHERECONFIG1000095
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 <VCFSP SVC Account> successfully added global
permissions for user <VCFSP SVC Account> <Cluster Name> not found YYYY/MM/DD HH:MM:SS ERROR : Not all ESXi Hosts in the cluster /<datacenter name>/host/<cluster name> are connected to the datastore /<datacenter name>/datastore/<vSAN cluster>.
ERR.INIT0001 - Validating configuration
Error:  Configuration error occurred. Invalid VCF Services runtime cluster name '<CLUSTER_NAME>'.

• This issue can also occur during Greenfield deployment of VCF 9.0

• The following errors are found in the logs at /var/log/vmware/vcf/domainmanager/domainmanager.log 
  

  "messages": [

  "id": "com.vmware.vcfms.bootstrap.InvalidClusterName",
"level": "ERROR",
"timestamp": "YYYY-DD-MMTHH:MM:SSZ",
"default": "Configuration error occurred. Invalid VCF services runtime cluster name '<CLUSTER_NAME>'. Please configure and retry the operation or contact support if the issue persists. [VCFMS-BOOTSTRAP-002]",
"stage": "INIT0001 - Validating configuration",
"args": [
"<CLUSTER_NAME>"

  "workflowName": "vsp-install-ozm4####thoh###jj5pju-297###817",
"messageCode": "VCFMS-BOOTSTRAP-002"

Environment

• VCF Automation
• VCF Operations 9.x
• VCF 9.1

Cause

• This issue occurs when there are spaces in the Datacenter name or the Cluster name.

  By design, Kubernetes resources (used within the VCF Services Platform) do not allow spaces, underscores (_), or uppercase letters in metadata.name according to Kubernetes RFC 1123 DNS naming constraints. If the vSphere object names contain these characters, the bootstrap process for the VCF Management Services cluster fails during the validation stage.

Resolution

To resolve this issue, rename the affected vSphere objects to adhere to naming standards:

1. Verify Datastore Mapping: Navigate to vCenter to verify that all ESXi hosts in the affected cluster are correctly mapped to the specified datastore.
2. Identify Naming Issues: Inspect the Datacenter and Cluster names for any spaces or unsupported characters (e.g., underscores or uppercase if strict compliance is required).
3. Rename Objects: If spaces or invalid characters are found, rename the Datacenter and/or Cluster in vCenter to remove them (e.g., change Production Cluster to production-cluster).
4. Retry Deployment: Re-run the VCF 9.0/9.1 Installation or Migration process.

Additional Information

Contact Broadcom Support