Home > Tintri VMstore™ > Knowledge Base > Tintri vSphere Web Client Plugin disappeared from the UI after upgrading vCSA to version 6.0U3

Tintri vSphere Web Client Plugin disappeared from the UI after upgrading vCSA to version 6.0U3

Applies To

 

Product(s)

Version(s)

Tintri vSphere Web Client Plugin

All

VMware vCenter Server Virtual Appliance (vCSA) 6.0U3

Description

 

Tintri vSphere Web Client Plugin disappeared from the UI after upgrading VMware vCenter Server Virtual Appliance (vCSA) to version 6.0U3

Symptoms

 

Tintri vSphere Web Client Plugin disappeared from the vCenter UI

 

The Tintri vSphere Web Client Plugin log (/opt/Tintri/VCP/running/logs/) is no longer updated after upgrading vCSA to version 6.0U3

 

Re-installing the Tintri vSphere Web Client Plugin does not correct the issue. Plus no errors noted during reinstall within /usr/tintri/TintriVCPInstallation.log 

 

The /storage/log/vmware/vsphere-client/wrapper.log after the upgrade to 6.0U3 shows the following error:

 

[WARN ] start-signalling-1          
o.s.core.io.support.PathMatchingResourcePatternResolver           Cannot search
for matching files underneath URL
[bundleresource://************:1/com/vmware/****/] because it does not
correspond to a directory in the file system java.io.FileNotFoundException: URL
[bundleresource://************:1/com/vmware/****/] cannot be resolved to
absolute file path because it does not reside in the file system:
bundleresource://************:1/com/vmware/****/
at org.springframework.util.ResourceUtils.getFile(ResourceUtils.java:205)
at org.springframework.core.io.AbstractFileResolvingResource.getFile(AbstractFileResolvingResource.java:52)

Resolution

 

Tintri vSphere Web Client Plugin reports the resource URL protocol as “BundleResource” where as in all previous versions of vCenter server the protocol used is “File”. This is caused when the vCSA 6.0U3 upgrade path doesn't update the wrapper.conf to refer to the updated jars and the web client server still refers to the older jars which are not available in the file path due to a VMware vSphere bug.

 

Workaround

 

To workaround the issue edit the wrapper.conf file to have it point to the jar files in the environment

 

After the edits are done within the wrapper.conf do a restart of the web client server service for changes to take effect.

 

Confirm Tintri vSphere Web Client Plugin appears in the UI

 

# Location of wrapper.conf file /usr/lib/vmware-vsphere-client/server/wrapper/conf/

 

As an example update the following variable to point to the new version of the .jar files:

set.OSGI_CLASSPATH=file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.nano.authentication_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.equinox.launcher_1.3.0.v20120308-1358.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.nano.shutdown_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.util.env_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.kernel.equinox.extensions_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/plugins/org.eclipse.osgi_3.8.2.v20130124-134944.jar

 

# You can find your version of jar typically in /usr/lib/vmware-virgo/server/lib/

 

 

Viewing 4 of 4 comments: view all
Tech approved - RD - 18/04/2017
Posted 15:34, 18 Apr 2017
Modified article formatting to match best practices. Article approved.
Posted 08:26, 24 Apr 2017
one very minor word tense change
Posted 22:51, 10 May 2017
After the edit of wrapper.conf of vCSA, we have to restart web client (sorry, this is for newbie):
#service-control --stop vsphere-client
#service-control --start vsphere-client

Also try to use I.E or Chrome for vCSA UI per VMware. Edited 19:11, 14 Jul 2017
Posted 19:08, 14 Jul 2017
Viewing 4 of 4 comments: view all
You must to post a comment.
Last modified

Tags

Classifications

This page has no classifications.