I see this behaviour in a pooled Linux Install, with RHEL 7.8:
Sometimes I get a desktop with an already logged in user or a session with a running "screensaver"
by some user.
I found out, that "horizon" loses the information, that the host is in use. (disconneted or active)
I'm using:
- VMware-horizonagent-linux-x86_64-7.9.0-13916467
And I have host1,..,hostN in the pool.
On the horizon server I can use the horizon admin API
https://horizon.domain/admin/
with this I can check which sessions are in use by "user1"
If I enter some the username "user1" the api shows:
- no active/disconneted sessions for user1 (it shows no session)
Now, when I connect with the the horizon client I get a logged session by user1 on hostX
My conclusion:
Some horizon component loses the information that the host is in use and serves
a still running desktop environment/session as "available"
I wrote a python script, which gets the active session in the pool:
- who | grep tty | cut -d " " -f 1 | sort -u
- and compares this with the state of the horizon api.
I can see, that this scenario is not uncommon.
Question:
- Is this already fixed?
