This issue is resolved in VMware ESXi 6.5 P04 and VMware ESXi 6.7 Update 3, available at
VMware Downloads.
Before performing an NSX-T upgrade, ESXi hosts should be upgraded to the fixed version.
Workaround:
To work around this issue if you do not want to upgrade, the ESXi host must be rebooted to clear the stale dvfilters.
There are 2 options
Automatic reboot all hosts during upgrade:
Change the group upgrade mode to reboot hosts by default as follows:
- Find the group id for the cluster using GET api/v1/upgrade/upgrade-unit-groups?component_type=HOST or from UI
- GET api/v1/upgrade/upgrade-unit-groups/<group id>
- In the above response, change extended_configuration value by updating {"key" : "rebootless_upgrade", "value" : "false"}.
- PUT the modified payload to api/v1/upgrade/upgrade-unit-groups/<group uuid>
or
Manual reboot of hosts
Post reboot, the NSX-T upgrade must be performed before exiting maintenance mode as moving VMs onto and off the host again may reintroduce the problem.
- Select to Pause the upgrade when an upgrade unit fails to upgrade.
- Start host upgrade.
- Once a host upgrade fails due to the issue described in this article:
a) Confirm the host is in vSphere maintenance mode and reboot it to clear the stale dvfilters.
b) Post reboot, the ESXi host should continue to remain in vSphere maintenance mode.
c) To retry the NSX-T upgrade, the host must be taken out of NSX maintenance mode.
Select System > Fabric > Nodes > Host Transport Nodes.
Select the ESXi host and from Actions and click "Exit Maintenance Mode".
If "Exit Maintenance mode" is not available, via the UI, use the API.
POST https://manager/api/v1/transport-nodes/{node_id}?action=exit_maintenance_mode.
d) On the Upgrade Coordinator, click Reset to clear the error.
e) Restart the host upgrade. It will now retry the problem host and allow the upgrade to proceed.