vSAN File Service remediation task fails after vCenter's domain name change

Products

• VMware vSAN 8.x

Issue/Introduction

After changing domain name on vCenter, File Service VMs may fail to redeploy in the workflow of File Service Remediation. 

This can be verified by examining value of ovfPackageUrl for EAM, via VCSA's logging. When encountered, previously used domain will be seen assigned to ovfPackageUrl variable, example, via /var/log/vmware/vsan-health/vmware-vsan-health-service.log: 

 

2025-12-16T14:59:13.355+01:00 INFO vsan-mgmt[#####] [VsanEamUtil::_GetAgency opID=vsan-PC-#############-###-###] Found agency 'eam.Agency:ce12828d-####-####-####-############' enabled with config: (eam.Agency.ConfigInfo) {
    dynamicType = <unset,
    dynamicProperty = (vmodl.DynamicProperty) [],
    agentConfig = (eam.Agent.ConfigInfo) [
       (eam.Agent.ConfigInfo) {
          dynamicType = <unset,
          dynamicProperty = (vmodl.DynamicProperty) [],
          productLineId = <unset,
          hostVersion = '6+',
          ovfPackageUrl = 'https://OLD-DOMAIN.local:443/vsanHealth/fileService/ovf/8.0.3.1000-24280767/VMware-vSAN-File-Services-Appliance-#######-######_OVF10.ovf',
          ovfSslTrust = <unset,
          ovfEnvironment = (eam.Agent.OvfEnvironmentInfo) {
          

Environment

VMware vSAN 8.x

vSAN File Services (All Versions)

Cause

After disabling vSAN cluster and manually changing vCenter domain name, the old OVF URL persists in EAM config.

This causes vSAN files service to report unhealthy status, FSVM fail to install on ESXi host(s) and 'Remediate File Service' task will fail with 'invalidUrl' thrown in /var/log/vmware/vsan-health/vmware-vsan-health-service.log, example: 

2025-12-09T13:18:46.672+01:00 ERROR vsan-mgmt[#####] [VsanClusterFileServiceSystemImpl::_RemediateClusterFileServiceTask opID=#####_#####] Exception happened in deploying OVF in cluster 'vim.ClusterComputeResource:domain-c####'
Traceback (most recent call last):
  File "bora/vsan/fileservice/vpxd/VsanClusterFileServiceSystemImpl.py", line 2691, in _RemediateClusterFileServiceTask
  File "bora/vsan/fileservice/vpxd/VsanEamUtil.py", line 140, in DeployOvfInCluster
  File "bora/vsan/fileservice/vpxd/VsanEamUtil.py", line 112, in SetupEamAgentDatastoreAndNetwork
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/pyEam/VmomiSupport.py", line 618, in <lambda>
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/pyEam/VmomiSupport.py", line 391, in _InvokeMethod
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/pyEam/SoapAdapter.py", line 1607, in InvokeMethod
pyEam.VmomiSupport.eam.fault.InvalidUrl: (eam.fault.InvalidUrl) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = '',
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   url = 'https://OLD-DOMAIN.local:443/vsanHealth/fileService/ovf/8.0.3.1000-24280767/VMware-vSAN-File-Services-Appliance-#####_########_OVF10.ovf',
   malformedUrl = false,
   unknownHost = false,
   connectionRefused = true,
   responseCode = <unset>
}

 

Resolution

Follow the steps as below to re-create the eam agency with the new ovf URL:

1.From VCenter UI: Administration -> vCenter Server Extensions -> vSphere ESX Agent Manager -> Configure tab -> delete agency for vsan-file-service

2.Monitor -> VSAN Health -> Infrastructure Health -> Remediate File Service