Back to bug 2125612
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2022-09-09 13:01:17 UTC | Target Release | 16.2 (Train on RHEL 8.4) | --- |
| Gregory Thiemonge | 2022-09-09 13:02:02 UTC | Keywords | Triaged | |
| Target Milestone | z4 | --- | ||
| Red Hat One Jira (issues.redhat.com) | 2022-09-09 13:05:49 UTC | Link ID | Red Hat Issue Tracker OSP-18639 | |
| Gregory Thiemonge | 2022-09-09 13:12:31 UTC | Target Milestone | --- | z2 |
| Keywords | Triaged | |||
| Assignee | njohnston | gthiemon | ||
| Target Release | --- | 17.0 | ||
| RHEL Program Management | 2022-09-09 13:12:40 UTC | Target Release | 17.0 | --- |
| Gregory Thiemonge | 2022-09-27 08:35:25 UTC | Target Milestone | z2 | z1 |
| Ihar Hrachyshka | 2022-11-15 15:17:52 UTC | CC | ihrachys | |
| Gregory Thiemonge | 2022-11-22 07:37:52 UTC | Target Milestone | z1 | zstream |
| Gregory Thiemonge | 2023-01-26 08:52:35 UTC | Target Release | --- | 17.1 |
| Target Milestone | zstream | beta | ||
| RHEL Program Management | 2023-01-26 08:52:43 UTC | Target Release | 17.1 | --- |
| Gregory Thiemonge | 2023-01-26 09:00:59 UTC | Link ID | OpenStack gerrit 847541 OpenStack gerrit 809996 | |
| Target Release | --- | 17.1 | ||
| RHEL Program Management | 2023-01-26 09:01:10 UTC | Target Release | 17.1 | --- |
| Gregory Thiemonge | 2023-01-26 09:03:35 UTC | Status | NEW | MODIFIED |
| Fixed In Version | openstack-octavia-worker-8.0.2-1.20221208181214.b0379d6.el9ost | |||
| Target Release | --- | 17.1 | ||
| RHEL Program Management | 2023-01-26 09:03:42 UTC | Target Release | 17.1 --- | --- 17.1 |
| Lon Hohberger | 2023-02-13 20:35:32 UTC | Fixed In Version | openstack-octavia-worker-8.0.2-1.20221208181214.b0379d6.el9ost | openstack-octavia-8.0.2-1.20221208181214.b0379d6.el9ost |
| errata-xmlrpc | 2023-02-20 10:53:27 UTC | Status | MODIFIED | ON_QA |
| Omer Schwartz | 2023-02-21 10:06:12 UTC | Status | ON_QA | VERIFIED |
| CC | oschwart | |||
| QA Contact | bbonguar | oschwart | ||
| Red Hat Bugzilla | 2023-05-24 06:54:33 UTC | CC | jvisser | |
| Andy Stillman | 2023-05-26 12:37:59 UTC | Flags | needinfo?(gthiemon) | |
| Gregory Thiemonge | 2023-05-30 09:03:49 UTC | Doc Text | Cause: Users may have experienced some warning messages in the Octavia Amphora VM logs ("nf_conntrack: table full, dropping packet") when the load balancer is loaded with a lot of concurrent sessions. Consequence: Some TCP flows may have been dropped by the Amphora VM, which could have added latency for the user traffic. Fix: conntrack is now disabled for TCP flows in the Octavia Amphora (it is only required for UDP flows) Result: New TCP flows are no longer dropped. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(gthiemon) | |||
| Jenny-Anne Lynch | 2023-06-02 10:24:39 UTC | CC | jelynch | |
| Doc Text | Cause: Users may have experienced some warning messages in the Octavia Amphora VM logs ("nf_conntrack: table full, dropping packet") when the load balancer is loaded with a lot of concurrent sessions. Consequence: Some TCP flows may have been dropped by the Amphora VM, which could have added latency for the user traffic. Fix: conntrack is now disabled for TCP flows in the Octavia Amphora (it is only required for UDP flows) Result: New TCP flows are no longer dropped. | Before this update, users may have experienced the following warning message in the Load-balancing service (octavia) Amphora VM log file when the load balancer was loaded with multiple concurrent sessions: `nf_conntrack: table full, dropping packet`. This error occurred if the Amphora VM dropped Transport Control Protocol (TCP) flows and caused latency on user traffic. With this update, connection tracking (contrack) is disabled for TCP flows in the Load-balancing service Amphora VM, and new TCP flows are not dropped. Conntrack is only required for User Datagram Protocol (UDP) flows. | ||
| Joanne O'Flynn | 2023-06-12 10:16:01 UTC | Doc Text | Before this update, users may have experienced the following warning message in the Load-balancing service (octavia) Amphora VM log file when the load balancer was loaded with multiple concurrent sessions: `nf_conntrack: table full, dropping packet`. This error occurred if the Amphora VM dropped Transport Control Protocol (TCP) flows and caused latency on user traffic. With this update, connection tracking (contrack) is disabled for TCP flows in the Load-balancing service Amphora VM, and new TCP flows are not dropped. Conntrack is only required for User Datagram Protocol (UDP) flows. | Before this update, users might have experienced the following warning message in the Load-balancing service (octavia) Amphora VM log file when the load balancer was loaded with multiple concurrent sessions: `nf_conntrack: table full, dropping packet`. This error occurred if the Amphora VM dropped Transport Control Protocol (TCP) flows and caused latency on user traffic. With this update, connection tracking (conntrack) is disabled for TCP flows in the Load-balancing service Amphora VM, and new TCP flows are not dropped. Conntrack is only required for User Datagram Protocol (UDP) flows. |
| CC | joflynn | |||
| Jenny-Anne Lynch | 2023-07-19 14:25:11 UTC | CC | jelynch | |
| Ian Frangs | 2023-08-11 15:32:10 UTC | CC | ifrangs | |
| Doc Text | Before this update, users might have experienced the following warning message in the Load-balancing service (octavia) Amphora VM log file when the load balancer was loaded with multiple concurrent sessions: `nf_conntrack: table full, dropping packet`. This error occurred if the Amphora VM dropped Transport Control Protocol (TCP) flows and caused latency on user traffic. With this update, connection tracking (conntrack) is disabled for TCP flows in the Load-balancing service Amphora VM, and new TCP flows are not dropped. Conntrack is only required for User Datagram Protocol (UDP) flows. | Before this update, users might have experienced the following warning message in the amphora log file of the Load-balancing service (octavia) when the load balancer was loaded with multiple concurrent sessions: `nf_conntrack: table full, dropping packet`. This error occurred if the amphora dropped Transport Control Protocol (TCP) flows and caused latency on user traffic. With this update, connection tracking (conntrack) is disabled for TCP flows in the Load-balancing service that uses amphora, and new TCP flows are not dropped. Conntrack is only required for User Datagram Protocol (UDP) flows. | ||
| errata-xmlrpc | 2023-08-16 00:03:42 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:12:09 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-16 01:12:09 UTC | |||
| errata-xmlrpc | 2023-08-16 01:12:36 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 |
Back to bug 2125612