Cannot enable vSAN file service when the AD has trusted domains in a separate network

Products

• VMware vSAN

Issue/Introduction

Symptoms:
vSAN below 7.0U2
Error Message :
('com.vmware.vsan.fileservice.fault.containercreationfailures.unknownerror', 'File server creation failed due to unkown reason.

vsanmgmtd.log:

2021-07-07T07:47:40.068Z info vsand[18148296] [opID=5ba2f1c9-W806-dafc-W4107 VsanFileServiceSystemImpl::_waitForContainersUp] failed container: ['10.x.x.248', '10.x.x.249', '10.x.x.250', '10.19.22.251'] err msgs are: {'10.x.x.249': 'Unknown container start up failure', '10.x.x.248': 'Unknown container start up failure', '10.x.x.250': 'Unknown container start up failure', '10.x.x.251': 'Unknown container start up failure'}
2021-07-07T07:47:40.077Z info vsand[18148296] [opID=5ba2f1c9-W806-dafc-W4107 VsanFileServiceSystemImpl::_waitForContainersUp] IP failed to come up: 10.x.x.249, failureKeyMsg: ('com.vmware.vsan.fileservice.fault.containercreationfailures.unknownerror', 'File server creation failed due to unkown reason. Contact Vmware Support for more information')

Environment

VMware vSAN 7.0.x

Cause

Container creation failure due to Unable to join Trusted AD Domains

Resolution

Upgrade vCenter/ESXi to 7.0U2 or higher

Workaround:
Enable file services without AD and later Plan an upgrade to vSAN 7.0 U2

Additional Information

Impact/Risks:
vSAN File service creation fails with Trusted AD domains