When re-enabling vSAN File Services, the error "Domain not configured. File service is enabled. In order to be able to create file shares, the file service domain must be configured" appears.

Products

• VMware vSAN 7.x
• VMware vSAN 8.x

Issue/Introduction

• The file service domain is already configured
• A vDS migration of FSVMs may have occured prior to the alert
• Multiple vSAN File Service OVF versions are present on the vCenter server 
• A recent vCenter and/or File Services upgrade has taken place.

 

Resolution

1) Remove unnecessary File Service OVF directories and files on the vCenter appliance.

2) Manually upload the correct OVF as part of the domain configuration (in many instances, the previous successful working OVF prior to your recent upgrade).

3) Re-enable vSAN File Service

Steps:

• SSH/Putty onto the VCSA
• type cd / and Enter
• Perform a global search on the VCSA for "OVF" related to vSAN File Services. The files should be located in /storage/updatemgr/vsan/fileService...
  • Type: find / -type f -name "*.ovf" 2>/dev/null

• Navigate to the relevant folder: cd /storage/updatemgr/vsan/fileService
• Remove the unnecessary OVF(s).
  • The below command is without confirmation.

    CAUTION:

    Do not remove the OVF folder for the currently used vSAN File Service version. Removing the active OVF files may prevent the vCenter from properly deploying or remediating the FSVMs.

    The rm -rf command is powerful and deletes files and directories without confirmation. Double-check the path and folder name before executing.

    :
    • Replace <OVF-VERSION-FOLDER> with the actual name of the folder you wish to remove (e.g., ovf-8.0.3.1000): rm -rf ovf-<OVF-VERSION-FOLDER>
      • example: rm -rf ovf-8.0.3.1000-24022510
      • type: ls -lar and confirm the folder has been removed:

• Re-enable vSAN File Service: Cluster > Configure > vSAN > Services > File Service > Enable
• Select "Manually load OVF", browse to the correct OVF and click Enable

FSVMs will now be successfully deployed.