Plugin upgrade fails on new HTML5 client on vsphere 6.5, works fine on Flex client

[virat1234]

Our plugin has 3 parts inside its zip file

UI-1.war -> Flex UI components

UI-2.war -> HTML UI components

service.jar -> Java services for both UI components.

The plugin installs and works fine on both clients, but fails when we upgrade the plugin by changing the version in the ExtensionManager. The flex client downloads and updates the plugin just fine. On the other hand, the HTML5 client does the following

1. Un-deploys the older version -> Any users already logged and using the plugin cannot use the plugin anymore. (the flex client does not do any such thing)
2. Tries to deploy the new version and fails
3. No error logs at all, it looks like it passes all the checks and then just stops working.

Is there any logging I can increase to see what is happening?

Virat

[laurentsd]

Search the vsphere_client_virgo.log for your plugin id (warnings or errors) and also the browser javascript console for errors.

Is it vSphere HTML Client 6.5 GA or a recent Fling release?

[virat1234]

I have been looking in the vsphere_client_virgo.log file and could not find any error messages. Are there any debug logs I can look at? Any specific package that I should enable DEBUG logging on?

Yes, it is the vSphere HTML client 6.5 GA.

Virat

[laurentsd]

I don't think debug logging will help but you can set it in server/configuration/serviceability.xml by changing <root level="INFO"> to <root level="DEBUG">

Otherwise attach your compressed virgo log, with the time of the upgrade problem, and I'll check it out.

[_vladi_]

Hi Virat,

Performance of plugin deployment has been improved in the HTML Client which resulted in a race condition during upgrade that was not present in the slower Flex Client. This has already been fixed and will be released with a next Fling and a next official release.

To clarify if you are running into the same problem could you please check your logs for lines like these?

[2017-05-04T01:00:05.420Z] [INFO ] plugin-deploy14 70000728 100033 200017 org.eclipse.virgo.medic.eventlog.default XF1000I Deploying plugin package 'com.vmware.myplugin' version 'X.Y.Z'.
[2017-05-04T01:00:05.420Z] [INFO ] plugin-deploy14 70000728 100033 200017 org.eclipse.virgo.medic.eventlog.default XF1001I Deployed plugin package 'com.vmware.myplugin' version 'X.Y.Z'.

This reports the plugin has been deployed but there are no traces of the plugin bundles being deployed in between. As a result the plugin will not be visible on the UI.

Is this what you are seeing with your plugin upgrade?

Cheers,

Vladi
 

[virat1234]

Yes, that is exactly what I am seeing. Also, right after the Deployed statement I see "failed to find message broker for myplugin-broker". Not sure if that is related.

[2017-06-27T22:54:27.760Z] [INFO ] plugin-deploy9               70000194 100018 200002 com.vmware.vise.extensionfw.impl.PackagesDeployer                 Deployed plugin package 'com.mycompany.plugin:5.1.483081'.

[2017-06-27T22:54:27.760Z] [INFO ] vc-extensionmanager-pool-121 70000194 100018 200002 com.vmware.vise.extensionfw.impl.PackagesDeployer                 Processed deployment success for plugin package 'com.mycompany.plugin:5.1.483081'.

[2017-06-27T22:54:27.761Z] [ERROR] vc-extensionmanager-pool-121 70000194 100018 200002 c.v.vise.messaging.amf.ClassDeserializationExtensionListener      Failed to find message broker for id MyCompany-broker

This was on Version 6.5.0.5600 of vCenter.

[_vladi_]

Yes, this issue is fixed now. Please retest it on the next releases.

For current versions the workaround is to restart the client.

Cheers,

Vladi