Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2116604

Summary: ovn-kubernetes Failed to handle external GW check
Product: OpenShift Container Platform Reporter: MD Tanzim Khorshed <mdkhorsh>
Component: NetworkingAssignee: obraunsh
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED DEFERRED Docs Contact:
Severity: medium    
Priority: medium CC: eglottma, mkennell, rravaiol, trozet
Version: 4.7Flags: mkennell: needinfo-
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-17 22:55:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description MD Tanzim Khorshed 2022-08-09 02:33:39 UTC 
Description of problem:

'Warning' reason: 'ErrorAddingLogicalPort' failed to handle external GW check: gateway specified for namespace <namespace name> with gateway addresses [] but no valid routes exist for pod: <podname>
^This is a legit bug in 4.9 and before. In 4.10 it has been fixed. The issue here is when the SPK is added and is serving an ICNI namespace, we will search all of the pods in the served namespace to update their routes to point to this new SPK. For some reason one of the pods in the namespace has no IPs, and thus we error out trying to add the SPK. The correct behavior should just be to warn that the pod IPs are missing and continue with adding the SPK (which is the current behavior in 4.10 and later):

https://github.com/openshift/ovn-kubernetes/blob/release-4.10/go-controller/pkg/ovn/egressgw.go#L243
Comment 4 Tim Rozet 2022-11-17 22:55:00 UTC 
Fix is being tracked in https://issues.redhat.com/browse/OCPBUGS-574