All the objects using the vSAN default policy (FTT=1) are stuck in "reduced-availability-with-no-rebuild" status.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• The customer is using a vSAN OSA cluster, and all the objects in the cluster are showing "reduced-availability-with-no-rebuild" status, which are using the FTT=1 vSAN default policy.
  
  
• All the ESXi hosts are healthy and contributing to the vSAN cluster; there are no issues with the disks on any of the ESXi hosts.
  
  
• When the user runs the "esxcli vsan debug object health summary get" command, they see that all the objects are in the "reduced-availability-with-no-rebuild" state.

Health Status                                              Number Of Objects
---------------------------------------------------------  -----------------
remoteAccessible                                                           0
inaccessible                                                               0
reduced-availability-with-no-rebuild                                     234
reduced-availability-with-no-rebuild-delay-timer                           0
reducedavailabilitywithpolicypending                                       0
reducedavailabilitywithpolicypendingfailed                                 0
reduced-availability-with-active-rebuild                                   0
reducedavailabilitywithpausedrebuild                                       0
data-move                                                                  0
nonavailability-related-reconfig                                           0
nonavailabilityrelatedincompliancewithpolicypending                        0
nonavailabilityrelatedincompliancewithpolicypendingfailed                  0
nonavailability-related-incompliance                                       0
nonavailabilityrelatedincompliancewithpausedrebuild                        0
healthy                                                                    0

Environment

VMware vSAN 7.0.x

VMware vSAN 8.0.x

Cause

• In a vSAN three-node standard cluster, all the objects should be healthy if all the ESXi nodes in the vSAN cluster are functioning properly and contributing to the storage. 
  
  
• When the user checks the clom logs, they see the following excerpts.

2025-04-07T07:02:31.034Z error clomd[2099882] [Originator@6876 opID=1804576233] CLOM_CheckClusterResourcesForPolicy: Not enough Upper FD's available. Available: 1, needed: 3
2025-04-07T07:02:31.034Z error clomd[2099882] [Originator@6876 opID=1804576233] CLOM_GenerateObjectConfig: Cluster doesn't have resources for the current iteration: objVersion: 15 replicas: 1, stripes: 1
2025-04-07T07:02:31.034Z error clomd[2099882] [Originator@6876 opID=1804576233] CLOMGenerateNewConfig: Failed to generate a configuration: Not found
2025-04-07T07:02:31.034Z error clomd[2099882] [Originator@6876 opID=1804576233] CLOM_Diagnose: There are currently 1 usable fault domains. The operation requires 2 more usable fault domains.

• There is only one fault domain available, and this is the reason why all the objects are stuck in the "reduced-availability-with-no-rebuild" status. To apply the vSAN default policy, the user needs three fault domains to satisfy the FTT=1 policy.
  
  
• When the user checks for the fault domain, they notice that all the ESXi hosts are in a single fault domain. The user can check the fault domain information via the following steps.
  
  
  • Navigate to the vSAN cluster.
  • Click the Configure tab.
  • Under vSAN, click Fault Domains.

Resolution

• In a vSAN standard three-node cluster, all three ESXi hosts need to reside in their own single-host fault domain. 
  
  
• To resolve this issue, the user needs to remove the existing fault domain, which contains all three ESXi hosts. After removing the existing single fault domain, all the ESXi hosts will reside in their own single-host fault domain, which will satisfy the three fault domains, and the object will resync to satisfy the FTT=1 policy, and eventually the objects will be healthy.

Additional Information

Managing Fault Domains in vSAN Clusters

Remove Selected Fault Domains