Quickstart failing to configure vSAN hosts when expanding existing cluster
search cancel

Quickstart failing to configure vSAN hosts when expanding existing cluster

book

Article ID: 383564

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

When adding additional hosts to an existing vSAN cluster via Quickstart the process does not complete. The Qucikstart configuration screen shows similar to the following:

The vSAN Skyline health check has an error for HOST COMPLIANCE CHECK FOR HYPERCONVERGED CLUSTER CONFIGURATION.

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

Environment

All versions of vSAN

Cause

There is an error detected by the vSAN health service preventing Quickstart from continuing. This may be an error related to other settings or connectivity issues.

If no error is present in the Skyline health check for vSAN, look on the vCenter server via ssh at /var/log/vmware/vsan-health/vmware-vsan-health-summary-result.log and look for any yellow or red errors to be addressed.

Log message example, details will vary per environment and problem:

2024-11-18T17:15:37.981Z INFO vsan-mgmt[2896732] [VsanHealthSummaryLogUtil::PrintHealthResult opID=agw-0355622-224b] Cluster vsan8  Overall Health : red
   Group cluster health : red
      Test timedrift health : green
      Test vsanesavlcmcheck health : green
      Test advcfgsync health : red
         AdvancedVsanConfigurationInSync: Option  Value  HostsWithThatValue
                                          (Vsan.Clombgprorebalancethreshold, 25, Host-4790, Host-4763, Host-4793, Host-4751,

 

Resolution

  1. Place all non configured hosts into maintenance mode if not already and remove from the cluster. - Note that all hosts that are showing as not configured must be removed before adding any to the cluster.
  2. Resolve the issue causing the health alert.
  3. Use the Quickstart wizrad to add the hosts to the cluster.

Note: If the cluster has production running on it make sure the hosts that need to be placed in to maintenance mode will not impact production in anyway. If it will a maintenance window will need to be scheduled for down time before proceeding.