Back to bug 1762298
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dan Winship | 2019-10-16 13:06:42 UTC | Version | 3.9.0 | 3.11.0 |
| Dan Winship | 2019-10-16 13:07:21 UTC | Blocks | 1762300 | |
| Dan Winship | 2019-10-16 13:07:38 UTC | Blocks | 1762301 | |
| Dan Winship | 2019-10-16 13:09:50 UTC | Link ID | Github openshift/kubernetes/pull/89 | |
| Eric Paris | 2019-10-16 17:19:12 UTC | Target Release | 4.2.z | --- |
| Dan Winship | 2019-10-16 18:51:29 UTC | Target Release | --- | 4.3.0 |
| Dan Winship | 2019-11-04 12:43:14 UTC | Blocks | 1768436 | |
| Dan Winship | 2019-11-04 12:46:06 UTC | Status | NEW | VERIFIED |
| Link ID | Github openshift/kubernetes/pull/89 | |||
| Summary | backport kube-proxy fix for spurious connection resets | kube-proxy fix for spurious connection resets | ||
| Dan Winship | 2020-01-08 14:50:42 UTC | Doc Text | Cause: In clusters with high network traffic where some packets are getting dropped, a previously-working connection to a service might suddenly fail with a "Connection reset by peer" error. Consequence: Clients would need to reconnect and retry; transferring large amounts of data might be difficult. Fix: An update was made to the iptables rules so they will handle TCP retransmits correctly. Result: Connections that have been successfully established will remain established until they are closed. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2020-01-22 20:53:31 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2020-01-23 11:07:48 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-01-23 11:07:48 UTC | |||
| errata-xmlrpc | 2020-01-23 11:08:16 UTC | Link ID | Red Hat Product Errata RHBA-2020:0062 | |
| Vedanti Jaypurkar | 2021-01-26 03:32:43 UTC | CC | vjaypurk | |
| Flags | needinfo?(danw) | |||
| Dan Winship | 2021-01-26 14:30:21 UTC | Flags | needinfo?(danw) |
Back to bug 1762298