Bug 1917609 - [4.6z] Deleting an exgw causes pods to no longer route to other exgws
Summary: [4.6z] Deleting an exgw causes pods to no longer route to other exgws
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Tim Rozet
QA Contact: Anurag saxena
: 1917608 (view as bug list)
Depends On: 1917605
Blocks: 1917608
TreeView+ depends on / blocked
Reported: 2021-01-18 22:47 UTC by Tim Rozet
Modified: 2021-02-08 13:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1917605
Last Closed: 2021-02-08 13:51:25 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 421 0 None closed Bug 1917609: Fixes deleting exgw pod 2021-02-10 12:04:54 UTC
Red Hat Product Errata RHSA-2021:0308 0 None None None 2021-02-08 13:51:43 UTC

Description Tim Rozet 2021-01-18 22:47:32 UTC
+++ This bug was initially created as a clone of Bug #1917605 +++

Description of problem:
Consider a scenario where multiple pods to be external gateways for pod such as:

ovn-worker1                     ovn-worker2  
pod A----OVN--eth0 ----------- External GW Pod1 (
                       |----- External GW Pod2 (
                       |------ cluster default gateway (

pod A now has 2 ecmp routes to, and Now, we delete External GW Pod1. pod A should still use as its only other ECMP gateway. Instead, we see that deleting External GW Pod1, results in a delete for the ovn_cluster_router policy for this pod A. This causes traffic from pod A to now go via the default cluster gateway ( .

Comment 1 Tim Rozet 2021-01-18 22:49:27 UTC
*** Bug 1917608 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2021-02-08 13:51: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.6.16 security and 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.