Back to bug 7834

Who When What Removed Added
samuel 2022-02-09 13:43:47 CET See Also https://www.cendio.com/bugzilla/show_bug.cgi?id=425
samuel 2022-02-09 13:44:09 CET See Also https://www.cendio.com/bugzilla/show_bug.cgi?id=7833
samuel 2022-02-09 13:44:26 CET See Also https://www.cendio.com/bugzilla/show_bug.cgi?id=3707
samuel 2022-02-09 13:45:03 CET See Also https://www.cendio.com/bugzilla/show_bug.cgi?id=3707 https://www.cendio.com/bugzilla/show_bug.cgi?id=3808
samuel 2022-02-09 13:45:23 CET Blocks 3707
samuel 2022-02-09 13:46:31 CET Target Milestone --- 4.15.0
samuel 2022-02-16 08:48:49 CET Acceptance Criteria * The admin should be able to use tlctl from the master to see load information about the agents in the cluster.

* Using the load status data from tlctl the admin should be able to predict decisions made by the load balancer.

* The load output from tlctl should be easy to understand.

* The tlctl subcommand should give a helpful error message when trying to run without root/sudo permissions.

* The tlctl subcommand should give a helpful error message when the vsmserver service isn't running.
Keywords relnotes
Assignee bugzilla-qa samuel
samuel 2022-02-24 14:45:21 CET Acceptance Criteria * The admin should be able to use tlctl from the master to see load information about the agents in the cluster.

* Using the load status data from tlctl the admin should be able to predict decisions made by the load balancer.

* The load output from tlctl should be easy to understand.

* The tlctl subcommand should give a helpful error message when trying to run without root/sudo permissions.

* The tlctl subcommand should give a helpful error message when the vsmserver service isn't running.
* The admin should be able to use tlctl from the master to see load information about the agents in the cluster.

* It should be possible to compare the number of users per agent in the cluster.

* Agents which are down should be clearly marked as down.

* Agents in different subclusters must be listed separately.

* Using the load status data from tlctl the admin should be able to predict decisions made by the load balancer.

* The load output from tlctl should be easy to understand.

* The tlctl subcommand should give a helpful error message when trying to run without root/sudo permissions.

* The tlctl subcommand should give a helpful error message when the vsmserver service isn't running.
tobfa 2022-03-01 11:19:11 CET CC tobfa
Assignee samuel tobfa
tobfa 2022-03-02 08:50:09 CET Acceptance Criteria * The admin should be able to use tlctl from the master to see load information about the agents in the cluster.

* It should be possible to compare the number of users per agent in the cluster.

* Agents which are down should be clearly marked as down.

* Agents in different subclusters must be listed separately.

* Using the load status data from tlctl the admin should be able to predict decisions made by the load balancer.

* The load output from tlctl should be easy to understand.

* The tlctl subcommand should give a helpful error message when trying to run without root/sudo permissions.

* The tlctl subcommand should give a helpful error message when the vsmserver service isn't running.
* The admin should be able to use tlctl from the master to see load information about the agents in the cluster.

* It should be possible to compare the number of users per agent in the cluster.

* Agents which are down should be clearly marked as down.

* Agents in different subclusters must be listed separately.

* Using the load status data from tlctl the admin should be able to predict decisions made by the load balancer.

* The load output from tlctl should be easy to understand.

* The tlctl subcommand should give a helpful error message when trying to run without root/sudo permissions.

* The tlctl subcommand should give a helpful error message when the vsmserver service isn't running.

* Output should fit standard terminal width (80 columns)
tobfa 2022-03-25 10:47:37 CET Status NEW RESOLVED
Resolution --- FIXED
ossman 2022-03-29 09:57:48 CEST Status RESOLVED REOPENED
Resolution FIXED ---
tobfa 2022-03-29 10:00:19 CEST Comment 77 is private 1 0
tobfa 2022-03-31 08:52:39 CEST Status REOPENED RESOLVED
Resolution --- FIXED
ossman 2022-03-31 09:37:16 CEST Status RESOLVED REOPENED
Resolution FIXED ---
ossman 2022-04-01 12:40:12 CEST Keywords ossman_tester
tobfa 2022-04-04 16:21:54 CEST Status REOPENED RESOLVED
Resolution --- FIXED
linma 2022-04-05 10:30:31 CEST CC linma
ossman 2022-04-07 11:18:10 CEST Status RESOLVED REOPENED
Resolution FIXED ---
ossman 2022-04-08 08:51:51 CEST See Also https://www.cendio.com/bugzilla/show_bug.cgi?id=7886
tobfa 2022-04-13 17:05:06 CEST Status REOPENED RESOLVED
Resolution --- FIXED
tobfa 2022-04-14 12:39:31 CEST Status RESOLVED REOPENED
Resolution FIXED ---
tobfa 2022-04-14 15:03:53 CEST Resolution --- FIXED
Status REOPENED RESOLVED
ossman 2022-04-22 14:30:36 CEST Status RESOLVED CLOSED
tobfa 2023-03-21 09:31:49 CET See Also https://bugzilla.cendio.com/show_bug.cgi?id=8121
tobfa 2023-04-28 16:38:39 CEST See Also https://bugzilla.cendio.com/show_bug.cgi?id=8145

Back to bug 7834