Please provide your feedback in this short Flings' survey.
A fully supported version of the HTML5 client is released with vSphere 6.5, and the official name will be vSphere Client.  We won't be renaming this Fling, but may start saying things like 'vSphere Client Fling' in addition to the other terms we've used before. Fling features are not guaranteed to be implemented into the product.
Oct 13, 2019

Hi,

Are the bug on the 'bugs' tab ever acknowledged or updated with status ?

Two problems I have with the HTML5 client would like your feedback on:

1. When editing permissions and adding an AD group, this can take several minutes to find the group name you've entered when you have a very large AD domain. In the old flex client you selected the domain name, entered a group name, and clicked the 'CHECK' button and it validated this instantly. Managing AD permissions with the HTML5 client is impossible - please fix!

2. The 'recent tasks' bar. If I click the filter icon next the 'initiator' field, it allows you to enter some text to filter by. As you start typing, the recent tasks list is updated in the background and you lose the text you were typing so it's impossible to use. Would also like a generic search bar for searching (all fields) of the recent task bar.

3. Management of vFlash is missing from the client. Only vFlash Read Cache has been deprecated but you've actually removed all support for vFlash Host Cache which has not been deprecated. Also, third party vendors rely on devices being allocated to vFlash (but not used for vFRC). Please readd support as the client is not 'feature complete' because of this.

Other than those 3 items .. great work :) !!

Jan 06, 2020

Hi Derek,

Thanks for sharing the feedback, 2 and 3 are getting fixed. 1 would need a bit more digging.

Sep 19, 2019

Kaloyan, for some reason I cant reply to you in the thread so here goes...

Here are the result of the commands you asked me to run:

cat /usr/local/bin/vsphere-h5-client-installer/installedVersion
4.3.0

rpm -qa | grep vsphere
vsphere-h5-client-4.3.0-14483008.noarch
vsphere-client-config-ui-1.0.0.0-14143519.noarch

Sep 19, 2019

I just loged into the 5480 port and saw this which I find quite strange

Vendor:
VMware, Inc.
Appliance Name:
vSphere Web Client Appliance
Appliance Version:
4.2.0.0 Build 13172979
(
Details...
)
Upgrade to version 1.2.0.0
Last Check:
Failed to check for updates(Error downloading manifest. Please contact your vendor. The requested URL returned error: 404 Not Found URL: https://vapp-updates.vmware.com/vai-catalog/valm/vmw/b2cf1433-7156-4396-8711-8949e3ff19eb/4.2.0.0.latest/manifest/manifest-latest.xml) on Thursday, 2019 September 19 09:10:55 UTC+2

Oct 01, 2019

Do you perhaps have to to respond to my posts? I cannot proceeed until you guys reply...

Oct 08, 2019

Hi Garth,
Sorry for the delay. I will check and try to respond tomorrow.

Oct 09, 2019

I appreciate it Kaloyan!!

Oct 10, 2019

Hi Garth,
I see the RPMs look updated.
Can you login to the H5 client after the upgrade?
Does it work?
Can you please share the content of cat /var/log/upgrade.log at my email.
I think you have it.

Best regards,
Kaloyan Iliev

Oct 11, 2019

No such file sadly. Would it be possible to arrange a remote session with you to resolve this issue perhaps? Otherwise I'm affriad that it will take months before it's fixed.

Oct 11, 2019

Oeps... wrong server lol

Self Extracting installer

vsphere-h5-client-4.3.0-14483008.noarch.rpm
vsphere-client-config-ui-1.0.0.0-14143519.noarch.rpm
stopping client config ui...

> vsphere-client-config-ui@1.0.0 stop /usr/lib/vmware-client-configui
> forever stopall

[32minfo[39m: Forever stopped processes:
[90mdata[39m: [37m [39m [37muid[39m [90mcommand[39m [90mscript[39m [37mforever[39m [37mpid[39m [37mid[39m [35mlogfile[39m [33muptime[39m
[90mdata[39m: [0] 5bwK [90m/usr/lib/nodejs/lin64/bin/node[39m [90msrc/server/main.js[39m 2739 2748 [35m/root/.forever/5bwK.log[39m [33m0:0:1:39.226[39m
Waiting for vSphere Client to stop: 0 seconds

vSphere Client stopped!
Preparing... ########################################
Updating / installing...
vsphere-client-config-ui-1.0.0.0-14143########################################
vsphere-client-config-ui rpm post-install scripts. Logs are available in: /usr/lib/vmware-client-configui/vmware-client-configui-install.log
Preparing... ########################################
Updating / installing...
vsphere-h5-client-4.3.0-14483008 ########################################
h5-client rpm post-install scripts. Logs are available in: /usr/lib/vmware-vsphere-ui/server/vsphere-ui-rpm.log
/root

Oct 11, 2019

I cant believe it... I just tried to log in again & it's working...???? 4.3.0

Oct 11, 2019

Should ovf imports be working in this build?

Oct 15, 2019

Okay thanks well in that case I have an issue with not being able to roll out ovf templates. I assume that 4.4.0 won't be as long a wait as 4.3.0? If so I'll just wait for it...

Sep 17, 2019

I'm unable to upgrade to 4.3.0 from 4.2.0, it hangs at Waiting for vSphere Client to stop: 183 seconds, and continues to wait and the seconds keep increasing.

I need to reboot the appliance in order to be able to access it, but it still at 4.2.0.

Manually updating using the shell also doesn't work. Downloading the .bsx works fine, but when executing it, it immeidately returns to the shell and nothing happened:

vsphereclient:~ # ./installer-4.3.0.bsx

Self Extracting installer

Please reload the UI and configure the Fling again!

Sep 18, 2019

Hi Frnak,
It should start another upgrade process in the background.
Please give it some time. You can check the upgrade logs at:
cat /var/log/upgrade.log
And the current version in:
cat /usr/local/bin/vsphere-h5-client-installer/installedVersion
If you still have problems you can try to manually stop the service both H5 and configui service and then start the upgrade.

service vsphere-ui stop
service vsphere-ui status
/etc/init.d/configui stop
/etc/init.d/configui status

Best regards,
Kaloyan Iliev

Sep 18, 2019

Hi,

unfortunately that doesn't work. I have manually stopped the services, but the upgrade log keeps repeating 'waiting for vSphere Client to stop:

vsphereclient:~ # service vsphere-ui stop
vsphereclient:~ # service vsphere-ui status
vsphere-ui.service - H5 vSphere Web Client
Loaded: loaded (/usr/lib/systemd/system/vsphere-ui.service; enabled)
Active: failed (Result: signal) since Wed 2019-09-18 23:58:08 CEST; 7min ago
Docs: https://labs.vmware.com/flings/vsphere-html5-web-client
Process: 23083 ExecStop=/usr/local/bin/vsphere-ui stop (code=exited, status=0/SUCCESS)
Process: 1315 ExecStart=/usr/local/bin/vsphere-ui start (code=exited, status=0/SUCCESS)
Main PID: 1404 (code=killed, signal=KILL)

Sep 18 00:17:09 vsphereclient vsphere-ui[1315]: Starting vSphere Client Web Server
Sep 18 23:58:01 vsphereclient vsphere-ui[23083]: Stopping vSphere Client Web Server
Sep 18 23:58:06 vsphereclient vsphere-ui[23083]: Tomcat did not stop in time.
Sep 18 23:58:06 vsphereclient vsphere-ui[23083]: To aid diagnostics a thread dump has been written to standard out.
Sep 18 23:58:06 vsphereclient vsphere-ui[23083]: Killing Tomcat with the PID: 1404
Sep 18 23:58:07 vsphereclient vsphere-ui[23083]: The Tomcat process has been killed.
Sep 18 23:58:08 vsphereclient vsphere-ui[23083]: .
Sep 18 23:58:08 vsphereclient vsphere-ui[23083]: rm: cannot remove ‘/usr/lib/vmware-vsphere-ui/server/pid.log’: No such file or directory
vsphereclient:~ # /etc/init.d/configui stop
stopping client config ui...

> vsphere-client-config-ui@1.0.0 stop /usr/lib/vmware-client-configui
> forever stopall

info: No forever processes running
vsphereclient:~ # /etc/init.d/configui status
requesting status for client config ui
info: No forever processes running

vsphereclient:~ # cat /var/log/upgrade.log

Self Extracting installer

vsphere-h5-client-4.3.0-14483008.noarch.rpm
vsphere-client-config-ui-1.0.0.0-14143519.noarch.rpm
stopping client config ui...

> vsphere-client-config-ui@1.0.0 stop /usr/lib/vmware-client-configui
> forever stopall

info: No forever processes running
Waiting for vSphere Client to stop: 0 seconds
Waiting for vSphere Client to stop: 3 seconds
Waiting for vSphere Client to stop: 6 seconds
Waiting for vSphere Client to stop: 9 seconds
Waiting for vSphere Client to stop: 12 seconds
....
Waiting for vSphere Client to stop: 366 seconds
Waiting for vSphere Client to stop: 369 seconds

Nov 21, 2019

I am having the same issue. This happened the last time I tried to upgrade as well. All processes are stopped but it never starts the install.

Nov 24, 2019

Only solution for me was to completely delete the HTML 5 Fling VM and redeploy it.

Nov 24, 2019

Yeah, I've ended up having to do that every time now. Good to know I'm not alone. Disappointing it's still having the same issues years later. VMware "upgrades" of anything are starting to become a meme.

Sep 16, 2019

Hi guys, how can I check the version of the installed Fling?
Want to create Ansible playbook to check and update Fling as needed.

Sep 18, 2019

Hi Sergey,
You can check the version at:
cat /usr/local/bin/vsphere-h5-client-installer/installedVersion
You can check the upgrade log at:
cat /var/log/upgrade.log
Best regards,
Kaloyan Iliev

Sep 18, 2019

Hi Sergey,
You can check the version at:
cat /usr/local/bin/vsphere-h5-client-installer/installedVersion
You can check the upgrade log at:
cat /var/log/upgrade.log
Best regards,
Kaloyan Iliev