Bug 7916 - Agents subcluster association does not show up in load information
Summary: Agents subcluster association does not show up in load information
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-03 16:03 CEST by William Sjöblom
Modified: 2022-05-10 12:38 CEST (History)
0 users

See Also:
Acceptance Criteria:

Attachments
tlwebadm status section with all subcluster configuration commented out (14.39 KB, image/png)
2022-05-03 16:03 CEST, William Sjöblom 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description William Sjöblom cendio 2022-05-03 16:03:03 CEST 
Created attachment 1035 [details]
tlwebadm status section with all subcluster configuration commented out

Given non-existent subcluster configuration or one that does not declare any agents, you can start a session just fine, but tlwebadm and tlctl does not show any load information. A possible scenario where this would happen is if `agents=...' is mistyped as `agent=...'.

We fall back on an agent on 127.0.0.1 which is present in the load information sent to tlwebadm and tlctl but not presented. Error messages or warning is given by neither the services nor tlctl.

This has been observed in both 4.14.0 and 4.14.0post.
Note You need to log in before you can comment on or make changes to this bug.