Error after upgrading vCenter in a vSAN cluster with ELM: "Unable to extract requested data. Check vSphere Client logs for details"
search cancel

Error after upgrading vCenter in a vSAN cluster with ELM: "Unable to extract requested data. Check vSphere Client logs for details"

book

Article ID: 392077

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptom:

After upgrading one of your vCenter Servers in a vSAN cluster with ELM, you see the following error under vSAN Health and vSAN performance:

 "Unable to extract requested data. Check vSphere Client logs for details."

 

Validation:

In the vSphere Client log file: /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log, you see the following errors pointing to an issue loading the plugin in the UI

 
 
[WARN ] packages-discoverer-pool-104  com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer   Unable to construct plugin server URL from . Skipping this Extension.ServerInfo entry for com.vmware.vsan.client:8.0.203.10000 com.vmware.vise.extensionfw.impl.remote.MalformedRemotePluginServerUrlException: Empty host name is not allowed.
at com.vmware.vise.extensionfw.impl.remote.RemotePluginServerUrl.constructRemoteUrl(RemotePluginServerUrl.java:70)
at com.vmware.vise.extensionfw.impl.remote.RemotePluginServerUrl.<init>(RemotePluginServerUrl.java:49)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer.buildRemotePluginServerInfos(VcPackagesDiscoverer.java:437)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer.buildRemotePackage(VcPackagesDiscoverer.java:326)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer.constructRemotePackage(VcPackagesDiscoverer.java:273)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer.buildDiscoveredVcPackages(VcPackagesDiscoverer.java:194)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer.getVcPackages(VcPackagesDiscoverer.java:174)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer$1.call(VcPackagesDiscoverer.java:102)
at com.vmware.vise.plugin.extension.discovery.VcPackagesDiscoverer$1.call(VcPackagesDiscoverer.java:95)
at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:826)
at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:1240)
at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.run(ExecutorUtil.java:1259)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at com.vmware.vise.util.concurrent.WorkerThreadFactory$1.run(WorkerThreadFactory.java:64)
at java.lang.Thread.run(Thread.java:750)

Environment

VMware vSAN 8.x

Resolution

To resolve the issue, update all vCenter Servers in the cluster to the same version