I have added the libraries folder where the plugin is installed at /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.vcplugin.plugin-1.2.1.27 path.
With the above packages added to the libraries folder, I was able to resolve all the OSGI dependencies except for the org.springframework.orm package. This issue persists on the OSGI console even if the plugin is uninstalled.
After restarting the VCSA 8.0 we get plugin deployment timeout, which eventually fails as shown below.
The plugin code is written in Springboot having the Spring version 4.3.9.RELEASE and SpringBoot version 1.5.9.RELEASE. Now, this plugin works perfectly on VCSA 7.0 but not on VCSA 8.0. I have a finding that the issue that might cause the plugin to not be compatible with VCSA 8.0 is the old spring version as mentioned in the article: https://kb.vmware.com/s/article/87880.
So I upgraded the plugin to Spring version 5.2.22.RELEASE and SpringBoot version to 2.0.9.RELEASE.
After this major upgrade, many packages were deprecated as SpringBoot was upgraded from 1. x to 2. x. After this major upgrade, I did some package name changes as suggested in the official Spring Documentation. After that also the plugin gets timed out.
Another thing is on UI we see the plugin type as local but from my observation plugin should be treated as remote and this might be an issue from UI.
Here is the plugin-package.xml:
Equinox.log:
vsphere_client_virgo.log:
vsphere-ui-runtime.log.stdout:
In Brief @Denis_Chorbadzh please let me know the answers to the following questions:
1. Is vSphere Client VCSA 8.0 compatible with Spring Version 4.3.9.RELEASE or do we need to upgrade Spring to 5.2.22_RELEASE ?
2. With help from the above attachments do you have any idea why is the plugin getting deployment timed-out after the upgrade?
3. Plugin type is seen as local on UI. But from my understanding this plugin is a remote plugin as my plugin is not running from VCSA. So is this affecting the deployment on VCSA 8.0?
4. Also after the spring boot upgrade to 2.0.9.RELEASE two dependencies again go into the INSTALLED state i.e. vcplugin-controller and vcplugin-ui. Do we need to add any jar to the libraries folder to resolve them?
5. If the plugin is getting installed on the VCSA 8.0, is there any way to access it just like APIs from postman? How to verify that it is successfully deployed/installed on the VCSA 8.0 and that the only issue lies on the UI side?
6. Any open-source repository for developing remote plugins on the VMware client plugin VCSA 8.0?
Best Regards,
Shivam