Bugzilla – Activity log for bug 8552: Penalty points need to be reimagined
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | New Account
- | Log In
- | Forgot Password
Back to bug 8552
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| tobfa | 2025-03-24 09:00:12 CET | Assignee | bugzilla-qa | tobfa |
| Target Milestone | --- | 4.19.0 | ||
| tobfa | 2025-03-24 09:00:33 CET | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=4429 | |
| tobfa | 2025-03-24 09:01:05 CET | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=6131, https://bugzilla.cendio.com/show_bug.cgi?id=4805 | |
| tobfa | 2025-03-24 15:36:22 CET | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=7620 | |
| Acceptance Criteria | MUST: * Broken agents must be deprioritized * Agent selection should adhere to the load balancer |
|||
| tobfa | 2025-03-24 15:37:03 CET | Acceptance Criteria | MUST: * Broken agents must be deprioritized * Agent selection should adhere to the load balancer | MUST: * Broken agents must be deprioritized * Agent selection must adhere to the load balancer |
| tobfa | 2025-03-25 12:19:17 CET | Summary | Penalty points are no longer relevant | Penalty points need to be reimagined |
| tobfa | 2025-03-25 12:29:41 CET | Acceptance Criteria | MUST: * Broken agents must be deprioritized * Agent selection must adhere to the load balancer | MUST: * Broken agents must be deprioritized * Agent selection must adhere to the load balancer SHOULD: * Add missing documentation |
| tobfa | 2025-03-25 12:34:22 CET | Acceptance Criteria | MUST: * Broken agents must be deprioritized * Agent selection must adhere to the load balancer SHOULD: * Add missing documentation | MUST: * Broken agents must be deprioritized * The deprioritization must have some erosion mechanism * Agent selection must adhere to the load balancer SHOULD: * Add missing documentation |
| tobfa | 2025-04-01 08:33:32 CEST | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=7039 | |
| tobfa | 2025-04-01 08:55:16 CEST | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=8561 | |
| tobfa | 2025-04-01 09:07:17 CEST | Acceptance Criteria | MUST: * Broken agents must be deprioritized * The deprioritization must have some erosion mechanism * Agent selection must adhere to the load balancer SHOULD: * Add missing documentation | MUST: * Faulty agents must be deprioritized SHOULD: * Add missing documentation |
| tobfa | 2025-04-08 09:59:49 CEST | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=8568 | |
| tobfa | 2025-04-09 16:59:15 CEST | Acceptance Criteria | MUST: * Faulty agents must be deprioritized SHOULD: * Add missing documentation | system should be documented at a high level, leaving burdening details MUST: * Faulty agents must be deprioritized * The penalty system must not be inert since fails are likely caused by persistent issues * Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable bounds * Faulty agents must not cause serious disturbances during low or high login frequencies SHOULD: * The penalty system should be able to be toggled off * The load balancer should log decisions due to the penalty system * The penalty |
| tobfa | 2025-04-10 13:28:23 CEST | Acceptance Criteria | bounds * Faulty agents must not cause serious disturbances during low or high login frequencies SHOULD: * The penalty system should be able to be toggled off * The load balancer should log decisions due to the penalty system * The penalty system should be documented at a high level, leaving burdening details MUST: * Faulty agents must be deprioritized * The penalty system must not be inert since fails are likely caused by persistent issues * Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable | bounds * Faulty agents must not cause serious disturbances during low or high login frequencies SHOULD: * Using tlctl or tlwebadm, admins should be able to see if agents are failing * The load balancer should log decisions due to the penalty system * The penalty system should be documented at a high level, leaving burdening details MUST: * Faulty agents must be deprioritized * The penalty system must not be inert since fails are likely caused by persistent issues * Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable |
| tobfa | 2025-04-11 19:24:07 CEST | Acceptance Criteria | bounds * Faulty agents must not cause serious disturbances during low or high login frequencies SHOULD: * Using tlctl or tlwebadm, admins should be able to see if agents are failing * The load balancer should log decisions due to the penalty system * The penalty system should be documented at a high level, leaving burdening details MUST: * Faulty agents must be deprioritized * The penalty system must not be inert since fails are likely caused by persistent issues * Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable | bounds * Faulty agents must not cause serious disturbances during low or high session startup frequencies SHOULD: * Using tlctl or tlwebadm, admins should be able to see if agents are failing * The load balancer should log decisions due to the penalty system * The penalty system should be documented at a high level, leaving burdening details MUST: * Faulty agents must be deprioritized * The penalty system must not be inert since fails are likely caused by persistent issues * Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable |
| tobfa | 2025-04-15 10:43:30 CEST | Acceptance Criteria | MUST: * Faulty agents must be deprioritized * The penalty system must not be inert since fails are likely caused by persistent issues * Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable bounds * Faulty agents must not cause serious disturbances during low or high session startup frequencies SHOULD: * Using tlctl or tlwebadm, admins should be able to see if agents are failing * The load balancer should log decisions due to the penalty system * The penalty system should be documented at a high level, leaving burdening details | MUST: • Failing agents must be deprioritized by the load balancer • The new penalty system be designed with the new load balancer in mind • The penalty system must not be inert decisions due to the penalty system • The penalty system should be documented at a high level, leaving out burdening details COULD: • Using tlctl or tlwebadm, admins should be able to see if agents are failing, since agent issues are likely persistent • Penalties must have some erosion mechanism that returns an agent to normal sorting within reasonable bounds • Scenarios handled well by the previous penalty system must remain well-handled SHOULD: • Failing agents should not inhibit users in scenarios with low session startup frequencies • Failing agents should not inhibit users in scenarios with high session startup frequencies • The load balancer should log |
| tobfa | 2025-04-15 15:55:59 CEST | Keywords | relnotes | |
| tobfa | 2025-04-15 16:27:02 CEST | Resolution | --- | FIXED |
| Status | NEW | RESOLVED | ||
| samuel | 2025-04-23 09:39:14 CEST | Keywords | samuel_tester | |
| CC | samuel | |||
| samuel | 2025-04-23 16:03:49 CEST | Status | RESOLVED | CLOSED |
Back to bug 8552