vic-admin vsphere session timeout leads to weird errors on the screen

[vburenin]

1. Log into vic-admin UI. Do not use it for a while(several hours I guess).
2. Refresh the page, you will still be logged into vic-admin UI, but lots of errors will be displayed regarding to the connection to vSphere API.

vSphere session timeout is just a guess, it might be something else. Unfortunately, all related data including logs is no longer available.

[anchal-agrawal]

@vburenin Did you see a screen like the second picture here #3106 (comment)?

This is expected behavior currently. It was implemented in #3106 towards issues #2811 and #3082. One UX improvement we can make is to prompt the user that logging out and in again could resolve the session issue.

[vburenin]

@anchal-agrawal So, you are saying it is a know bug that is a less even than the other. Ok. Let's keep it open.

[anchal-agrawal]

I came across this screen today:

The error message was improved in #3270 to prompt the user to re-login. If you saw the same screen, we can close this issue since this is expected behavior.

[gigawhitlocks]

This is by design

[vburenin]

@gigawhitlocks This design has to be improved.

[gigawhitlocks]

@vburenin with regard to the planning we did this week, probably doesn't make much sense to spend a lot of time refining this UI.

I initially had vicadmin log the user out in this case and @anchal-agrawal was told to change it to do what it does now. The messaging about "Logging in again may resolve the issue" was added to clarify things in this situation.

I don't personally think it's worth spending the time to change this behavior, but if you do then you should bring it up with @hickeng et al and then you should be able to open an issue with a specific description of the agreed-upon behavior.

This issue is worded like this is a bug, which it is not.

[vburenin]

@gigawhitlocks I am not pushing to address it right now, it should be addressed at some point eventually.This bug can just stay open until it is addressed.