Bug 1917608

Summary: [4.6z] Deleting an exgw causes pods to no longer route to other exgws
Product: OpenShift Container Platform Reporter: Tim Rozet <trozet>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: high CC: anusaxen
Version: 4.6.z   
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1917605 Environment:
Last Closed: 2021-01-18 22:49:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1917605, 1917609    
Bug Blocks:    

Description Tim Rozet 2021-01-18 22:47:01 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 (172.0.0.4)
                       |
                       |----- External GW Pod2 (172.0.0.5)
                       |
                       |------ cluster default gateway (172.0.0.1)
 

pod A now has 2 ecmp routes to 172.0.0.4, and 172.0.0.5. Now, we delete External GW Pod1. pod A should still use 172.0.0.5 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 (172.0.0.1) .
Comment 1 Tim Rozet 2021-01-18 22:49:27 UTC 

*** This bug has been marked as a duplicate of bug 1917609 ***