vSAN File Service VMs are not deployed after enablement due to error ""Cannot complete the operation. See the event log for details. Unable to enable the vSAN file service: Failed to deploy OVF in cluster"

Products

• VMware vSAN

Issue/Introduction

• After enabling vSAN File Service, the vSAN File Service Node VMs are not deployed.
• Same or similar errors during enablement/configuration occur:

  • Cannot complete the operation. See the event log for details. Unable to enable the vSAN file service: FSVM does not exist from the beginning.

  • Cannot complete the operation. See the event log for details. Unable to enable the vSAN file service: Failed to deploy OVF in cluster 'vim.ClusterComputeResource:domain-c##' with error: (vmodl.fault.InvalidArgument) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = '', faultCause = <unset>, faultMessage = (vmodl.LocalizableMessage) [], invalidProperty = 'config.scope' }.

Environment

VMware vCenter Server
VMware vSAN

Cause

When EAM (ESX Agent Manager) agencies are not healthy (e.g. are in a disabled state in the database), the automated deployment of vSAN File Service Nodes is not working as expected as its also using and dependent on EAM.

Resolution

Please follow the steps outlined in the Resolution-section of KB to address this:
vCLS VMs do not deploy due to the EAM Agency showing as "Disabled" following a vSAN Cluster Shutdown