Create VSAN File service domain fails with unknown reason.

Products

• VMware vSAN

Issue/Introduction

- Create VSAN Fille service domain task fails with error File service creation failed due to unknown reason

- Cannot enable VSAN FS with the AD domain option enabled. (It can, however, be enabled without if deployed without the AD domain)

 

Environment

VMware vSAN 8.0.x

Cause

This issue occurs when set_spn fails from time to time, because there is unreachable AD/LDAP server when attempting to integrate Active Directory with the file service. 

- In vmware-vsan-health-service.log files you can see following entries:

2024-10-10T13:03:49.239+02:00 ERROR vsan-mgmt[07914] [VsanClusterFileServiceSystemImpl::_CreateDomain opID=agw-0017217-1a2f-XXXXXX] Failed to create domain VSANFS-DOMAIN

- In vsanmgmt..log files you can see following entries:

2024-10-10T10:53:14.070Z Er(11) vsand[2268916]: [opID=agw-0017217-1a2f-W26449-458e-XXXXXXX VsanFileServiceSystemImpl::CreateDomainFailureCleanup] Failed to remove ip XX.XX.XX.XX in domain fe4aa193-01a5-49d1-bb3c-XXXXX
2024-10-10T10:53:14.070Z Er(11)[+] vsand[2268916]:   msg = 'Failed to get the state of container fs-container-001 '

2024-10-10T10:37:06.711Z In(14) vsand[2268916]: [opID=agw-0017217-1a2f-W26449-458e-XXXXXXX VsanFileServiceSystemImpl::_waitForContainersUp] start waiting for containers: ['XX.XX.XX.XX', 'XX.XX.XX.XX']

2024-10-10T10:39:36.079Z Wa(12) vsand[2268916]: [opID=agw-0017217-1a2f-W26449-458e-XXXXXXX VsanFileServiceSystemImpl::_waitForContainersUp] Container XX.XX.XX.XX got failure: (vmodl.RuntimeFault) {
2024-10-10T10:39:36.079Z Wa(12)[+] vsand[2268916]:   msg = 'Failed to startup container fs-container-001: set_spn_timeout '
2024-10-10T10:39:36.079Z Wa(12)[+] vsand[2268916]: }. Keep waiting ..

Resolution

Workaround

Create FS domain gradually by following steps:

1. Create the file service domain with one container IP
2. Add containers into the file service domain one by one, by reconfiguring file service domain.
if file service domain creation failed, add the container or another container again, until all containers are added.

Additional Information

This is known issue that is resolved in ESXI 8.0U3 P05