Comment 1 Pierre Ossman 2025-04-15 13:35:31 CEST

The information that can be out of date is:

 * Numbers of users/sessions that have terminated (we poll every 10 minutes)
 * If the agent is responding (we poll every 40 seconds)

Comment 5 Hannes 2025-05-08 12:43:36 CEST

The feature was tested on tlwebadm by logging in and verifying in status>load that the number of users on the agent was automatically updated. One user was then logged out, and a page-refresh <F5> did not lower the number of users. The logged-out user was still displayed in status>sessions.
After clicking the “Refresh” button inside status>load, the correct number of users was shown and the information inside status>sessions was also updated.

>MUST:
>* It must be possible to force an update of load info.
Yes, this also checks the DOWN status of agents before the scheduled update.
>* Information that is shown in webadm must be synced with the internal state of the load balancer.
Yes, once refreshed with the button in status>load it displays updated information from the load balancer.
>SHOULD:
>* It should be accessible from webadm interface with a button.
Yes.
>COULD:
>* It could be automatically updated when internal load info changes.
No, this was skipped due to time constraint.

Comment 7 Linn 2025-05-08 14:51:35 CEST

Tested the following on RHEL 9 with server build 4042.

> MUST:
> * It must be possible to force an update of load info.
Yes, when clicking the refresh button, both the number of users as well as the agent status is updated. Note that for agent status, "Down" is the only that can be refreshed in this way. For "Draining", a restart of vsmserver is required, which triggers an update of the agent status.

If vsmserver is down when clicking refresh, the page is reloaded with an error message showing. This was tested with server build 4044, since the other build contained a bug which made Status/Load crash when vsmserver was down (see commit r41888, bug 5008).

> * Information that is shown in webadm must be synced with the internal state of the load balancer.
Yes, it shows the information the load balancer uses to take decisions. Since the load balancer sometimes uses slightly outdated information, this "old" information is what is shown as default on the Status/Load page.  

> SHOULD:
> * It should be accessible from webadm interface with a button.
Yes.

> COULD:
> * It could be automatically updated when internal load info changes.
No, if a data change occurs, the page needs to be refreshed to show the updated values.

---

I also tested the following areas that were affected by the code changes:
* 'tlctl session list', subcluster name completer (only available for root user)
* 'tlctl load list'
* Creating a new session
* Agent status still gets updated automatically every 40 seconds

Looked through commits and read release notes, looks good. Changed the wording in the documentation slightly for better flow.