vCenter VCSA 6.5.0U1b HTML Client not updated?

[ChrisSmith2]

The vCenter 6.5.0U1b update was released last Thursday (26 October 2017). I have deployed the update to a VCSA using the Server Appliance console (<ip>:5480). After rebooting, the Server Appliance reports the version as "6.5.0.11000 Build Number 6816762", and a release date of "October 26, 2017", and checking for updates states that the latest updates are installed.

However, logging in to the HTML Client, the "Help" > "About" page shows "vSphere Client version 6.5.0.10000" - the same as 6.5U1 - and issues reported against the 6.5U1 release that were expected to be fixed in the next official patch are still present (specifically https://communities.vmware.com/thread/571456). The Flex Client reports "Version 6.5.0.10000 Build 6816762".

Was the HTML Client updated between 6.5.0U1 and 6.5.0U1b? If so, was the fix above expected to be included? If not, when do you expect the next update to be released which does include the fix?

There is also an issue where navigating to a custom page via the "Home" drop-down menu does not update the node tree, and clicking the Global Refresh icon in the VMWare toolbar causes the entire UI to revert to whatever was last selected in the node tree (this only occurs in the HTML client, the Flex client works as expected) - this was previously reported outside of the forum. Is there any timeframe for that issue to be addressed?

[_vladi_ · Accepted solution]

Hi Chris,

The vSphere Client has been updated in 6.5.0U1b but the version is wrongly reported.

The expectation about the issue that requires reboot is to be released in one of the update/patch releases. It has already been fixed but we couldn't roll it out in 6.5.0U1b. Please stay tuned for another one, we will update the forum thread accordingly.

We tried checking the Global Refresh navigation problem again after discussing with you but could not reproduce it. Now that you report the same with the latest release we will pick it up again and retest on this build.

Cheers,

Vladi

[ChrisSmith2]

Thanks for clarifying, Vladi! I'll keep an eye out for the next update.

The release notes for 6.5.0U1b are now available, but don't mention the HTML Client. Are there any specific changes that plugin developers should be aware of, and/or does it align with any particular Fling (e.g. are any of the Fling 11 API changes included/supported)?

If you have any issues with the navigation problem repro, please drop me a PM and I can provide further details / screen recordings etc.

Thanks again as always for your help,

Chris.

[_vladi_]

Hi Chris,

6.5.0U1b has not been chosen as a release vehicle for any SDK-related changes so Fling 11 APIs are not part of it. That is why there has been no specific announcement for 6.5.0U1b on the forum.

We just retested the navigation problem issue and again no luck. What we are observing is that when you select your plugin item from the Home drop-down menu the Object navigator / tree on the left always updates appropriately. As a consequence the Global refresh works fine.

I am starting to think there might be something special in your plugin.xml declarations (like having a nodespec with viewOpenedUponFocus but no children nodespec or something like that). Could you please provide the relevant nodespec definitions from your plugin.xml? Let's see if we can reproduce it using those.

Thanks.

Cheers,

Vladi

[ChrisSmith2]

I've sent further details on our specific nodespec definition via PM. The nodespec follows the definition in the "vSphere Web Client SDK Documentation" for 6.5, "Adding a Pointer node to the Object Navigator", which doesn't mention the "viewOpenedUponFocus" entry.

BTW, the links for the current documentation (posted in your blog at "https://blogs.vmware.com/code/2017/07/14/vsphere-html-client-sdk-6-5-documentation-and-tools-resourc...") no longer work; both the online and PDF versions return a not found/not accessible error.

[ChrisSmith2]

Adding the "viewOpenedUponFocus" line from the 6.5U1 SDK "globalview" "plugin.xml" sample to our plugin fixes the global refresh issue. Thanks for the pointer!