Quickstart failing to configure vSAN hosts: Warrnig "Hyperconverged cluster configuration compliance"

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• When adding additional hosts, or readding previously used hosts, to an existing vSAN cluster via QuickStart the process does not complete. The QuickStart configuration screen shows similar to the following

• The vSAN Skyline health check has an error for "Hyperconverged cluster configuration compliance" or "Host Compliance Check for Hyperconverged Cluster Configuration"  with Recommendation of Invoke "Configure services" wizard to apply the hyperconverged cluster configuration to the host

 

             There may or may not be other alerts/warnings present in Skyline health.

Environment

VMware vSAN 7.x

VMware vSAN 8.x

Cause

• This issue can occur due to adding hosts to the vSAN cluster out side of the QuickStart wizard, or

• If Existing Hosts were removed from vSAN cluster, changes were made to it and they were readded.

• Since these changes were made out side of the QuickStart the alert was triggered.

• Current QuickStart workflow requires all hosts to be placed in Maintenance Mode and then added into the cluster via QuickStart.

Resolution

• The current issue of "Quick Start" being grayed out is expected if Hosts are added to clusters manually or via QuickStart.
  
  
• Currently there is only a workaround available, resolution for this issue is being considered for future release.

Workaround

Follow the steps below, 

Note: Take Snapshots of vCenter before performing below steps. Please Capture Offline snapshots for vCenter In linked Mode. 

1. Find out the cluster MOID from vpxd log like "domain-c10" for affected vSAN cluster
   
   From /var/log/vmware/vpxd/vpxd.log:
   
   2025-05-22T01:59:13.458Z info vpxd[22377] [Originator@6876 sub=drmLogger opID=ClusterSnapshot-d9527a4] Periodic dump section 142923690741 created for cluster [vim.ClusterComputeResource:domain-c10,Vsan2Cluster]
   
   or Use this command on the vCenter ssh : grep "vSAN_Cluster_Name" /var/log/vmware/vpxd/vpxd.log
   
   Note: This MOID can also be seen in the URL post selecting the affected vSAN cluster on the vSphere Client.
   
   
2. Backup /etc/vmware-vsan-health/silent.json by running this command "cp /etc/vmware-vsan-health/silent.json /tmp"
   
   
3. Run the following command from vCenter SSH by replacing the current cluster MOID 
   
   echo '{"domain-c10": {"cluster": ["hostinmm"]}}' > /etc/vmware-vsan-health/silent.json
   
   
4. Restart vsan health service by running this command "vmon-cli -r vsan-health"
   
   
5. Add affected host via QuickStart. (If affected host is in the cluster, place it in maintenance Mode and remote it out of the vSAN cluster ).
   
   
6. Repeat Step 5 for each affected hosts.
   
   
7. Once Completed, Recover the "silent.json" using the command "cp /tmp/silent.json /etc/vmware-vsan-health/silent.json".
   
   
8. Restart vsan health service by "vmon-cli -r vsan-health".

Re-Test vSAN Skyline Health, the "Host Compliance Check for Hyperconverged Cluster Configuration" check should be health now.

Additional Information

vSAN -- vSAN Healthcheck -- Host compliance check for hyperconverged Cluster configuration