From the browser console log:

"09:54:32.004 debug http GET[7] -> url: "/ovirt-engine/api/options/UserSessionTimeOutInterval", headers: {"Accept":"application/json","Authorization":"*****","Accept-Language":"en_US","Filter":true} transport.js:74:9"

"09:54:32.141 debug Reducing action: {"type":"SET_USER_SESSION_TIMEOUT_INTERVAL","payload":{"userSessionTimeoutInterval":-1}} utils.js:48:13"

Your engine "UserSessionTimeOutInterval" is set to -1. VM Portal is interpreting this as "auto-logout a second ago" instead of "do not auto-logout".

The simple fix is to set that value to something >0 in your engine configs.

I filed https://github.com/oVirt/ovirt-web-ui/issues/1085 to account for a -1 value properly in VM Portal.

On Thu, Aug 8, 2019 at 4:07 AM Matthias Leopold <matthias.leopold@meduniwien.ac.at> wrote:

Am 08.08.19 um 07:49 schrieb Scott Dickerson:
>
>
> On Wed, Aug 7, 2019 at 11:06 AM Sharon Gratch <sgratch@redhat.com
> <mailto:sgratch@redhat.com>> wrote:
>
> Hi,
> @Scott Dickerson <mailto:sdickers@redhat.com>, the session logout
> issue for VM portal 1.5.3 was handled in the following PRs:
> https://github.com/oVirt/ovirt-web-ui/pull/1014
> https://github.com/oVirt/ovirt-web-ui/pull/1025
>
> Any idea on what can be the problem?
>
>
> That is very strange. We saw a problem similar to that where, when
> web-ui is starting up, the time it took for the app to fetch the
> "UserSessionTimeOutInterval" config value was longer than the time it
> took to load the auto-logout component. In that case the value was
> considered to be 0 and auto logged the user out right away. That issue
> was dealt with in PR 1025 and the whole login data load process was
> synchronized properly in PR 1049.
>
> I need some additonal info:
> - The browser console logs from when the page loads to when they're
> logged out
> - the "yum info ovirt-web-ui"
>
> I'll be able to better triage the problem with that info.
>

Thanks to all for replies. I sent the requested info directly to Scott
Dickerson.

Matthias