Certain tasks in vCenter UI may result in 'Cannot complete file creation operation. There are currently 0 usable fault domains. The operation requires 3 more usable fault domains.'
Article ID: 385238
Updated On:
Products
Issue/Introduction
Tasks like
Moving VM from local datastore to vSAN datastore,
Creating a file using vCenter UI under vSAN datasture,
Clicking on vSAN datastore in vCenter UI,
May result in error message:
Cannot complete file creation operation. There are currently 0 usable fault domains. The operation requires 3 more usable fault domains.
Compatibility error when migrating VM from local to vSAN datastore:
Policy specified requires 3 fault domains contributing storage, but only 0 found
Environment
VMware vSAN 7.x
VMware vSAN 8.x
Cause
An insufficient number of Fault Domains are currently present in the environment.
An inaccessible Fault Domain may triger this issue.
A host that is not a part of the Fault Domain but is seeing the vSAN datastore may result in this situation.
Resolution
In a stretched cluster or 2 node cluster, ensure availability of 3 fault domains:
Click vSAN cluster > Configure Tab > Fault Domains under vSAN.
In a standalone cluster, Individual hosts are in their own fault domain hence minimum required is 3 hosts for FTT RAID1.
If a host in vSAN cluster is in maintenance mode and is impacting availability of required fault domains, it brought back into production.
If a host is in network partition, this should be resolved.
Click vSAN cluster > Monitor Tab > Skyline Health under vSAN > RETEST, look for network partition alerts.
Check all the disk groups are available on each host. If this is a new cluster, all disk groups should be created.
Does the task require more hosts or disk groups than available? Check storage policy used for the task and validate enough hosts and disk groups are available.
Try create test VMs on each host and address any issues. Click vSAN Cluster > Monitor Tab > Proactive Tests under vSAN > VM Creation Test.
If a host that used to be in the vSAN cluster was removed with out following guidelines may cause this issue.
Ask customer or look for host/hosts under the datacenter or vCenter that is not part of any other cluster but is still seeing the vSAN datastore from the cluster in question.
If there is such a host, place it in maintenance and follow the article to run the command 'esxcli vsan cluster leave' or reboot the host.
Feedback
