Registration of IOFilter VASA Provider Failed Alerts After Enabling vSphere Supervisor on vCenter 9.0.1

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Excessive events are generated on the VMware vCenter Server for VMware ESXi hosts after enabling the vSphere Supervisor.
  
  
• The ESXi Host > Monitor > Events page is saturated with VASA Provider registration failure messages as below :
  "Registration of a IOFilter VASA Provider [ESXi FQDN]:443/iofiltervp/version.xml failed - Port 1443 might be disabled on corresponding ESXi host or at Firewall level. Please refer kb#375445 for more info."
  
  
• The vCenter Server's journal logs will have several entries as below : 
  

  Feb 09 23:58:06 vcenter-server vpxd[2358222]: Event [########] [1-1] [####-02-09T23:58:06.484054Z] [vim.event.EventEx] [info] [VMware vCenter Storage Monitoring Service] [datacenter] [########] [Registration of a IOFilter VASA Provider https://esxi.domain.com:443/iofiltervp/version.xml failed - Port 1443 might be disabled on corresponding ESXi host or at Firewall level. ...>
  Feb 09 23:58:06 vcenter-server vpxd[2358222]: Event [########] [1-1] [####-02-09T23:58:06.761276Z] [vim.event.EventEx] [info] [VMware vCenter Storage Monitoring Service] [datacenter] [########] [Registration of a IOFilter VASA Provider https://esxi.domain.com:443/iofiltervp/version.xml failed - Port 1443 might be disabled on corresponding ESXi host or at Firewall level. ...>
  Feb 09 23:58:07 vcenter-server vpxd[2358222]: Event [########] [1-1] [####-02-09T23:58:07.036685Z] [vim.event.EventEx] [info] [VMware vCenter Storage Monitoring Service] [datacenter] [########] [Registration of a IOFilter VASA Provider https://esxi.domain.com:443/iofiltervp/version.xml failed - Port 1443 might be disabled on corresponding ESXi host or at Firewall level. ...>
  
  

• The SPS logs report the provider already exists after initiating a :
  

  ####-02-10T05:10:10.865Z [pool-47-thread-1] INFO  opId=sps-VICNotifier-697557-53 com.vmware.vim.sms.policy.PolicyManagerImpl - Starting Timer: ioFilterVpProcessOnHostRename. Host MoId host-##
  ####-02-10T05:10:10.912Z [pool-47-thread-1] INFO  opId=sps-VICNotifier-697557-53 com.vmware.vim.sms.provider.vasa.VasaProviderUtils - Latest IOFilter hosts: [esxi.domain.com, esxi2.domain.com ]
  ####-02-10T00:08:09.086Z [pool-47-thread-1] INFO  opId=sps-VICNotifier-619130-856 com.vmware.vim.sms.policy.PolicyManagerImpl - Timer stopped: ioFilterVpProcessOnHostRename, Time taken: 57 ms.
  ####-02-10T00:08:09.086Z [pool-29-thread-2] INFO  opId=sps-VICNotifier-619130-856 com.vmware.vim.sms.StorageManagerImpl - Starting Timer: registerProviderInt. Provider spec: (sms.provider.VasaProviderSpec) {
     dynamicType = null,
     dynamicProperty = null,
     name = IOFilter Provider esxi.domain.com,
     description = IOFilter VASA Provider on host esxi.domain.com,
     username = IOFilterUser,
     password = (not shown),
     url = https://esxi.domain.com:443/iofiltervp/version.xml,
     certificate = null
  }
  ####-02-10T00:08:09.093Z [pool-29-thread-2] ERROR opId=sps-VICNotifier-619130-856 com.vmware.vim.sms.provider.ProviderFactory - Provider with url https://esxi.domain.com:443/iofiltervp/version.xml already exists.
  ####-02-10T00:08:09.093Z [pool-29-thread-2] INFO  opId=sps-VICNotifier-619130-856 com.vmware.vim.sms.StorageManagerImpl - Timer stopped: registerProviderInt, Time taken: 7 ms.
  ####-02-10T00:08:09.093Z [pool-29-thread-2] INFO  opId=sps-VICNotifier-619130-856 com.vmware.vim.storage.common.vc.impl.VcQueryImpl - Starting Timer: getHostMoIdForHostNames.
  ####-02-10T00:08:09.093Z [pool-29-thread-2] INFO  opId=sps-VICNotifier-619130-856 com.vmware.vim.storage.common.vc.impl.VcQueryImpl - Timer stopped: getHostMoIdForHostNames, Time taken: 0 ms.

Environment

vSphere Supervisor 1.31
VMware vCenter Server 9.0.1.0
VMware ESXi 9.0.1.0 

Cause

Workload Control Plane (WCP) invokes a function that triggers spurious host rename notifications.
The Storage Provider Service (SPS) receives these false positive notifications and attempts to re-register the IOFilter VASA providers.

Because the providers already exist and the host names have not actually changed, the re-registration fails and continuously triggers harmless alerts in the UI.

Resolution

The IOFilter provider alerts are harmless and do not impact storage or compute functions.
Broadcom Engineering is aware of this issue and is working on a fix to be included in vCenter 9.1.0.