Bug 2086851 - pods with multiple external gateways may only be have ECMP routes for one gateway
Summary: pods with multiple external gateways may only be have ECMP routes for one gat...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Tim Rozet
QA Contact: Anurag saxena
Depends On:
Blocks: 2087203
TreeView+ depends on / blocked
Reported: 2022-05-16 16:48 UTC by Tim Rozet
Modified: 2022-08-10 11:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:12:25 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 1092 0 None open Bug 2086851: enable `exportloopref` linter and fix violations 2022-05-16 17:54:45 UTC
Github ovn-org ovn-kubernetes pull 2984 0 None Merged enable `exportloopref` linter and fix violations 2022-05-16 16:50:52 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:12:37 UTC

Description Tim Rozet 2022-05-16 16:48:07 UTC
Description of problem:
Due to a regression introduced by the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2070762

Pods served by multiple gateways may only have routes added for a single gateway. This is likely to happen when the served app pods are added after the serving gateways are created.

Comment 1 Tim Rozet 2022-05-16 16:50:53 UTC
Already fixed upstream by https://github.com/ovn-org/ovn-kubernetes/pull/2984

Comment 6 errata-xmlrpc 2022-08-10 11:12:25 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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.