Bug 2087203 - [4.10z] pods with multiple external gateways may only be have ECMP routes for one gateway
Summary: [4.10z] pods with multiple external gateways may only be have ECMP routes for...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Tim Rozet
QA Contact: Anurag saxena
Depends On: 2086851
Blocks: 2087226
TreeView+ depends on / blocked
Reported: 2022-05-17 14:51 UTC by OpenShift BugZilla Robot
Modified: 2022-05-31 12:41 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-05-31 12:40:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 1095 0 None open [release-4.10] Bug 2087203: enable `exportloopref` linter and fix violations 2022-05-17 15:57:29 UTC
Red Hat Product Errata RHBA-2022:4754 0 None None None 2022-05-31 12:41:06 UTC

Description OpenShift BugZilla Robot 2022-05-17 14:51:29 UTC
+++ This bug was initially created as a clone of Bug #2086851 +++

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.

--- Additional comment from trozet on 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-05-31 12:40:42 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.10.16 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.