Things I noticed when updating from 2015.10.22 to latest
Hi! Excellent work so far. I wish the production webclient were this fast. Here are my current gripes, feel free to tweet and discuss more @arielsanchezmor
Before we dig in, some things about the fling website:
The changelog doesn't have an entry for "2015.10.22" - I'm going to assume I was running v3. Either use v4 everywhere, or use "2015.12.21" everywhere... but try to be consistent :smileygrin: We're all accustomed to build numbers anyways for hosts and vCenter versions.
The Fling itself:
Creating a directory on a datastore is not intuitive. I finally put a \ next to the datastore name and typed my folder, but a little label saying "Select the folder or device where you want to create a folder and type the new folder name in the white space below" should be easy to add and would help.
I would really appreciate having the /vmfs path stated in the file browser, since that was the path I was going to give the Help/Update dialog to the upgrade vib. Instead I had to SSH into the host to find it, which defeats the purpose of upgrading through GUI. It would be even cooler that in the datastore browser, I could right-click on a vib file and choose install or update. Not too difficult considering you already support right click for delete and what not.
I see the task "Install Host Patch v2" completed - yay - but I don't have instructions now. Do I reboot? Restart a service? Logout and log back in? A small dialog would go a long way. Even if it's displayed right after the task is generated (without knowing if it succeeded or not) it would be helpful. I also think you could indicate where to check for logs (in \etc\var\... for example) in case the task fails so people can post meaningful errors or realize the esxcli software vib comamnd failed because of something self-inflicted.
After upgrading (at least I got a green tick on the task, so I'm assuming all is good), I logged out, refreshed my Chrome browser, logged back in and got this error (i've seen two other posts about it here and here with no answer). It seems to happen when the CEIP banner would be displayed.
Unhandled Exception (1)
Unfortunately, we hit an error that we weren't expecting.
The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.
I tried logging out and then logging back in through an incognito window and the error was gone, so there seems to be some cache-related cleanup missing in the upgrade procedure.
5. In incognito, I can't get the right facing triangle drop-downs on the left pane (on the left side of "Virtual Machines", "Storage", Networking" to work anymore. They appear to be grayed out. My old normal session only has the "Storage" one enabled and in black. This is very annoying.
After a host reboot the same behavior persisted in problems 4 and 5, for both my normal session and an incognito window. Thanks again for the great work so far!
