Bugzilla – Activity log for bug 7632: Agent permanently down if started when network is unavailable
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | New Account
- | Log In
- | Forgot Password
Back to bug 7632
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| frifl | 2021-01-26 14:01:55 CET | CC | frifl | |
| Assignee | bugzilla-qa | frifl | ||
| Target Milestone | --- | 4.12.1 | ||
| frifl | 2021-01-27 09:10:41 CET | Acceptance Criteria | , should not be allowed to communicate. * A DNS lookup that takes long time to complete should not lag or lock the ThinLinc system. * If an agent or HA node fails to look up any allowed clients, it should *not* result in that agent/node being permanently down. * If the DNS changes it should be reflected in the ThinLinc setup without needing to restart the services. * An old IP, no longer associated with an allowed client |
|
| ossman | 2021-01-29 16:42:25 CET | Keywords | relnotes | |
| frifl | 2021-02-01 13:46:44 CET | Acceptance Criteria | , should not be allowed to communicate. * A DNS lookup that takes long time to complete should not lag or lock the ThinLinc system. * If an agent or HA node fails to look up any allowed clients, it should *not* result in that agent/node being permanently down. * If the DNS changes it should be reflected in the ThinLinc setup without needing to restart the services. * An old IP, no longer associated with an allowed client | , should not be allowed to communicate. * If an agent or HA node fails to look up any allowed clients, it should *not* result in that agent/node being permanently down. * If the DNS changes it should be reflected in the ThinLinc setup without needing to restart the services. * An old IP, no longer associated with an allowed client |
| frifl | 2021-02-01 13:54:44 CET | Resolution | --- | FIXED |
| Status | NEW | RESOLVED | ||
| linma | 2021-02-01 15:56:11 CET | Keywords | linma_tester | |
| CC | linma | |||
| linma | 2021-02-02 17:13:38 CET | Status | RESOLVED | CLOSED |
Back to bug 7632