Unable to retrieve vSAN related information via HTML5 client after upgrading to vSphere 6.7 Update 3

Products

• VMware vSAN

Issue/Introduction

Symptoms:
VMware acknowledges an issue with the vSAN UI when using the HTML5 client after patching up to 6.7 Update 3 in an environment that started with vSphere 5.5 when initially deployed.

Note: Environments built initially on 6.x and later releases are NOT susceptible to this issue and may be upgraded without encountering this behavior

In Cluster -> Monitor -> Virtual Objects:

Failed to extract requested data. Check vSphere Client logs for details.

In Cluster -> Monitor -> Performance:

Unable to query data. Try again later.

In Cluster -> Monitor -> Capacity:

Failed to extract requested data. Check vSphere Client logs for details.

Environment

VMware vSAN 6.7.x

Cause

Logs contain entries similar to:

/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log
[ERROR] http-nio-5090-exec-7 com.vmware.vsan.client.services.ProxygenController service method failed to invoke java.lang.reflect.InvocationTargetException: null
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.vmware.vsan.client.services.ProxygenController.invokeService(ProxygenController.java:130)
        at com.vmware.vsan.client.services.ProxygenController.invokeServiceWithJson(ProxygenController.java:64)
        at sun.reflect.GeneratedMethodAccessor544.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)

Caused by: com.vmware.vsphere.client.vsandp.core.sessionmanager.common.NotAuthenticatedException: Authentication information for the specified site is missing. Authenticate with the site and try again.
        at com.vmware.vsphere.client.vsandp.core.sessionmanager.common.VcClient.getConnection(VcClient.java:91)
        at com.vmware.vsphere.client.vsandp.core.sessionmanager.common.VcClient.getConnection(VcClient.java:67)
        at com.vmware.vsphere.client.vsandp.core.sessionmanager.common.VcClient.getConnection(VcClient.java:63)
        at com.vmware.vsan.client.services.common.CeipService.getCeipServiceEnabled(CeipService.java:42)
        ... 119 common frames omitted
Caused by: com.vmware.vsphere.client.vsandp.core.sessionmanager.vlsi.client.sso.tokenstore.NoTokenException: No token for site:

NOTE: 
The log that needs to be verified resides on vCenter, it will be required to SSH into vCenter in order to verify it or from the DCUI by switching to the console pressing ALT + F1 if needed.

Resolution

This issue is resolved in vCenter 6.7 Update 3a

Additional Information

Note: When patching any vSAN cluster, it is critical to patch vCenter as well as ESXi.  If the ESXi hosts have been patched up to 6.7 Update 3, but vCenter is still on a previous build, the next step is to patch vCenter up to 6.7 Update 3 as well to ensure compatibility.

Unable to retrieve vSAN related information via HTML5 client after upgrading to vSphere 6.7 Update 3

Impact/Risks:
Unable to manage vSAN using the HTML5 client