Bug 2090315 - [4.9.z] LoadBalancer SCTP service leaves stale conntrack entry that causes issues if service is recreated
Summary: [4.9.z] LoadBalancer SCTP service leaves stale conntrack entry that causes is...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Surya Seetharaman
QA Contact: Anurag saxena
Depends On: 2080069 2111552
Blocks: 2111557
TreeView+ depends on / blocked
Reported: 2022-05-25 13:49 UTC by Pablo Alonso Rodriguez
Modified: 2022-09-29 07:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2080069
: 2111557 (view as bug list)
Last Closed: 2022-09-29 07:54:32 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 1192 0 None Merged [release-4.9] Bug 2105266: EGW: Clean Stale Conntrack Entries 2022-09-06 18:54:14 UTC
Github openshift ovn-kubernetes pull 1220 0 None Merged [release-4.9] Bug 2090315: Remove conntrack entries after rules 2022-09-03 12:22:58 UTC
Red Hat Product Errata RHBA-2022:6678 0 None None None 2022-09-29 07:54:42 UTC

Comment 6 Surya Seetharaman 2022-07-29 12:27:59 UTC
last piece of this which is to reorder the cleanup of conntrack entries is being done via: https://github.com/openshift/ovn-kubernetes/pull/1220

Comment 8 Alexander Pavel 2022-09-06 18:56:30 UTC
Please do not make github links linking to specific commits in a PR. This breaks various Github integrations in CI. Just link the full PR.

Comment 11 errata-xmlrpc 2022-09-29 07:54:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.9.49 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.