All Posts

Hi @Denis_Chorbadzh , As you suggested, we've added stax2, woodstox jars, and integrated the libraries directory into plugin.zip. Now we can see that the libraries folder getting extracted into /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/. Even with this change, we are still facing a timeout issue with our plugin. The org.springramework.orm unresolved dependency is still there but we're ignoring it as suggested and all the other dependencies are resolved/active. At this stage, we are able to see plugin entry into /mob and "Failed" entry at Administration -> Client Plug-Ins. The vsphere_client_virgo.log shows an ERROR for deployment mentioning timeout but does not tell anything else. Is there any other log to check or any debugging method to root cause the timeout issue? Please advice.     [2023-02-24T13:35:26.515Z] [INFO ] sdk-plugin-deployer-93 com.vmware.vise.plugin.status.LocalPluginStatusServiceImpl DEPLOYING: Deploying plugin package com.vcplugin.plugin:1.2.1.27 ... [2023-02-24T13:35:26.516Z] [WARN ] sdk-plugin-deployer-93 com.vmware.vise.extensionfw.impl.PackageManifestParser Plugin version mismatch for com.vcplugin.plugin between the plugin registration info (1.2.1.27) [2023-02-24T13:35:26.531Z] [INFO ] sdk-plugin-deployer-93 com.vmware.vise.extensionfw.impl.sandboxing.EsaBuilder Creating OSGi sandbox for package com.vcplugin.plugin with scope fullyIsolated [2023-02-24T13:35:27.476Z] [INFO ] plugin-deploy13 com.vmware.vise.extensionfw.impl.PackagesDeployer Deploying plugin package 'com.vcplugin.plugin:1.2.1.27'. [2023-02-24T13:35:27.476Z] [INFO ] plugin-deploy13 com.vmware.vise.extensionfw.impl.DeploymentEventLoggerImpl Event=PACKAGE_DEPLOY_BEGIN; Params=com.vcplugin.plugin, 1.2.1.27 [2023-02-24T13:45:26.841Z] [INFO ] plugin-discovery-bus-thread com.vmware.vise.vim.extension.PluginStatusTaskManager User: VSPHERE.LOCAL\vsphere-webclient-1c7d92d8-3b3b-4ec1-85ad-da68e934700d initiated plugin DOWNLOAD task for plugin com.vcplugin.plugin:1.2.1.27. [2023-02-24T13:45:26.863Z] [INFO ] plugin-discovery-bus-thread com.vmware.vise.vim.extension.PluginStatusTaskManager User: VSPHERE.LOCAL\vsphere-webclient-1c7d92d8-3b3b-4ec1-85ad-da68e934700d initiated plugin DEPLOYMENT task for plugin com.vcplugin.plugin:1.2.1.27. [2023-02-24T13:45:27.476Z] [ERROR] sdk-plugin-deployer-93 com.vmware.vise.extensionfw.impl.PackagesDeployer Package deployer timed out waiting for com.vcplugin.plugin:1.2.1.27; [2023-02-24T13:45:27.489Z] [ERROR] sdk-plugin-deployer-93 com.vmware.vise.plugin.status.LocalPluginStatusServiceImpl DEPLOYMENT_FAILED: Error deploying plugin package com.vcplugin.plugin:1.2.1.27. Reason: Plugin deployment has timed out. [2023-02-24T13:45:27.489Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Started validating com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.489Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Begin VmwareNameMisuseCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.490Z] [ERROR] plugin-deploy13 com.vmware.vise.extensionfw.impl.PackagesDeployer Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.vcplugin.plugin-1.2.1.27 java.lang.InterruptedException: null [2023-02-24T13:45:27.493Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService End VmwareNameMisuseCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.493Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Begin DynamicImportUsageCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.493Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService End DynamicImportUsageCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.493Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Begin RequireBundleUsageCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.493Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService End RequireBundleUsageCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.493Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Begin UnversionedPackageImportCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.493Z] [ERROR] sdk-plugin-deployer-93 com.vmware.vise.vim.extension.VcExtensionManager Deployment of plugin package: 'com.vcplugin.plugin:1.2.1.27' registered in vCenter Server: 'VCSA80.test.com (a25c1537-d8c0-4ff4-bd69-09e97a946de0)' has failed. java.util.concurrent.CompletionException: com.vmware.vise.plugin.deploy.PluginDeploymentException: Deployment of plugin: 'com.vcplugin.plugin:1.2.1.27' in vCenter server: 'VCSA80.test.com (a25c1537-d8c0-4ff4-bd69-09e97a946de0)' failed! Caused by: com.vmware.vise.plugin.deploy.PluginDeploymentException: Deployment of plugin: 'com.vcplugin.plugin:1.2.1.27' in vCenter server: 'VCSA80.test.com (a25c1537-d8c0-4ff4-bd69-09e97a946de0)' failed! [2023-02-24T13:45:27.493Z] [INFO ] sdk-plugin-deployer-93 com.vmware.vise.plugin.registry.VcExtensionStateRegistry Updating entry: Plugin: 'com.vcplugin.plugin:1.2.1.27', State: 'FAILED_DEPLOY' [2023-02-24T13:45:27.502Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService End UnversionedPackageImportCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.502Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Begin PluginPackageGlobalScopeCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.502Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService End PluginPackageGlobalScopeCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.502Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Begin PluginDeploymentExceptionCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.502Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService End PluginDeploymentExceptionCheck on com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.502Z] [INFO ] plugin-validation1 com.vmware.vise.extensionfw.impl.OsgiUsageValidationService Finished validating com.vcplugin.plugin:1.2.1.27 [2023-02-24T13:45:27.519Z] [WARN ] vice-extension-mngr-pool-144 com.vmware.vise.vim.extension.PluginStatusTaskManager Skip posting tasks for plugin package com.vcplugin.plugin:1.2.1.27: No task to update. This has no impact on plugin package deployment but is expected only during plugin development. In Production the plugin package should be registered as a vCenter extension. [2023-02-24T13:45:27.519Z] [ERROR] plugin-deploy13 com.vmware.vise.plugin.status.LocalPluginStatusServiceImpl DEPLOYMENT_FAILED: Error deploying plugin package com.vcplugin.plugin:1.2.1.27. Reason: Deployment error. java.lang.InterruptedException: null [2023-02-24T13:45:27.675Z] [ERROR] plugin-deploy13 com.vmware.vise.extensionfw.impl.DeploymentEventLoggerImpl Event=PACKAGE_DEPLOY_FAIL; Params=com.vcplugin.plugin, 1.2.1.27     The second thing is as mentioned in the document https://vdc-repo.vmware.com/vmwb-repository/dcr-public/77dd6491-bb96-47f3-8c2e-a5a4655f078b/b916bc3c-0168-4487-a9e5-c89b50373c18/Local-Plugins-Library-Isolation.pdf the libraries folder should be added in /usr/lib/vmware-vsphere-ui/plugin-packages/<Sample Plugin>. But we don't find any <Sample Plugin> package there. Note: VCSA80.test.com is just for example. In our environment, it is FQDN and is resolvable. Best Regards, Shivam

Hi @ShivamVerma380 ,   First, you need to integrate the "libraries" folder in your plugin.zip and not modify directly the plugin cache in "/etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/". This directory is used for downloading and unarchiving the plugin deliverables.   Regarding Spring 4.3.9, it is vulnerable to Spring4Shell, and we highly recommend you upgrade to 5.3.XX (LTS).   For vcplugin-ui, you need: - https://mvnrepository.com/artifact/org.codehaus.woodstox/woodstox-core-asl/4.4.1 and - https://mvnrepository.com/artifact/org.codehaus.woodstox/stax2-api Don’t mind the "org.springramework.orm" not being resolved: it is a red herring. It has bundle id of 129, typically plugin bundle ids are in 300 range. For vcplugin-controller, you need to resolve "org.springframwork.beans" jar first (it is the provider of "org.springframework.beans.factory.annotation").   From the attachments it is not clear why your “org.springframwork.beans” is not resolved (Note: there will be more than one “org.springframwork.beans”, yours will have id in the 300+ range). It is also not clear why the plugin deployment timed out. It was probably due to the unresolved plugin bundles.   Regarding the type of the plugin, your plugin is a "local" plugin. This means it will be downloaded from the remote location and will be placed inside the VCSA's tomcat server. To be a "remote" plugin, it needs to run on your own server and just provide its views to the vSphere Client. Remote plugins also use a different manifest format, called plugin.json. You can find more information about the remote plugin architecture here. Have in mind that the local plugin architecture is being deprecated and the next major vSphere Release will support only remote plugins.   Finally, you can verify your plugin is successfully installed by finding it in Administration -> Client Plug-Ins and checking its status. Additionally, you can inspect the vsphere_client_virgo.log file and search for your plugin ID to verify there are not errors and the deployment is successful.   Best Regards, Denis

Hi @Denis_Chorbadzh  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       

Hello  many thanks! Turns out I am an id... It is even easier than that. The NFS full-mount description is already the MOID. The reference to ha-datastoresystem is working just fine in this combination. e.g. <RemoveDatastore xmlns="urn:internalvim25"> <_this xsi:type="HostDatastoreSystem" type="HostDatastoreSystem" serverGuid="">ha-datastoresystem</_this> <datastore xsi:type="Datastore" type="Datastore">192.168.110.110:/mnt/NFS_HDD</datastore> </RemoveDatastore> Again, many thanks - Only now I started using the mob view on host and than it became obvious  

Pass the ManagedObjectReference(MOID) for both HostDatastoreSystem and Datastore( not the datastore name). https://vdc-repo.vmware.com/vmwb-repository/dcr-public/1ef6c336-7bef-477d-b9bb-caa1767d7e30/82521f49-9d9a-42b7-b19b-9e6cd9b30db1/vim.host.DatastoreSystem.html#removeDatastore Eg:   <soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <RemoveDatastore xmlns="urn:internalvim25"> <_this xsi:type="HostDatastoreSystem" type="HostDatastoreSystem">datastoreSystem-200</_this> <datastore xsi:type="Datastore">datastore-20</datastore> </RemoveDatastore> </soap:Body> </soap:Envelope>  

Hi @ShivamVerma380  If you use Spring MVC controllers in your plugin, here is a list of the bundles required to resolve Spring MVC dependencies: org.apache.servicemix.bundles.aopalliance-1.0_6 org.apache.servicemix.bundles.spring-aop-5.2.22.RELEASE_1 org.apache.servicemix.bundles.spring-beans-5.2.22.RELEASE_1 org.apache.servicemix.bundles.spring-context-5.2.22.RELEASE_1 rg.apache.servicemix.bundles.spring-context-support-5.2.22.RELEASE_1 org.apache.servicemix.bundles.spring-core-5.2.22.RELEASE_1 org.apache.servicemix.bundles.spring-expression-5.2.22.RELEASE_1 org.apache.servicemix.bundles.spring-web-5.2.22.RELEASE_1 org.apache.servicemix.bundles.spring-webmvc-5.2.22.RELEASE_1 Best Regards, Denis

Hi, We have tried to add the bundles mentioned above in the "libraries" folder which is parallel to the "plugins" folder on VCSA 8.0. Still, the issue persists on the OSGI console and we have 2 unresolved dependencies i.e. org.springframework.orm and org.eclipse.virgo.web.dm. org.springframework.orm is always in the "INSTALLED" state even if the plugin is not installed on VCSA 8.0. Looking forward to your help on this, Regards Shivam

There does not seem to be a forum area for the vSphere Web Services SDK, as such I will ask the moderators to look at this post and see where they think it sits best. Creating another post on the topic as you have done just results in duplicates. @Denis_Chorbadzh The next time you encounter a post that you think is in the wrong area, click the 3 vertical dots menu to the right and choose the Report Inappropriate Content option to leave a note for the moderators (like I'm going to do now)

Hi @cubits,   Unfortunately, we are not able to provide an adequate answer since this forum is concerned with vSphere Client extensibility and plug-ins. You can try posting your question in a relevant forum.   Best Regards, Denis

Hi,   The solution install token is a one-time token that is injected in the deployed VM and has a lifespan of 30 minutes. It is intended to be used for the solution's extension registration and, because of security concerns, cannot be regenerated. The "api/ui/solutioninstall" is an API of the vSphere UI and is not a part of the mentioned SDKs. You can find more information in the vSphere Client SDK official documentation. After the solution plugin has been registered, you can log in the vSphere UI, go to the plugin UI and initiate extension update by passing the session information to the plugin's backend which can obtain a vCenter Server session and call the vCenter Server APIs.   Best Regards, Denis