Bug 1986708

Summary: Single stack external gateway makes the pod not starting with dual stack clusters
Product: OpenShift Container Platform Reporter: Federico Paolinelli <fpaoline>
Component: NetworkingAssignee: Federico Paolinelli <fpaoline>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aconstan, anusaxen, mapandey, mcornea, trozet, yprokule
Version: 4.8   
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1977330 Environment:
Last Closed: 2021-10-12 06:01:19 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: 1977330    
Bug Blocks:    

Description Federico Paolinelli 2021-07-28 07:29:41 UTC
+++ This bug was initially created as a clone of Bug #1977330 +++

Description of problem:

Pod gets stuck in ContainerCreating when a gwip is single stack (i.e. ipv4 only) in a dual stack cluster

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
On a dual stack cluster:

1. Create a gw pod with annotations like:

      k8s.ovn.org/routing-namespaces: test
      k8s.ovn.org/routing-network: foo
      k8s.v1.cni.cncf.io/network-status: '[{"name":"foo","interface":"net1","ips":["172.19.0.5"],"mac":"01:23:45:67:89:10"}]'

2. Create a pod in the test namespace


Actual results:
Pod gets stuck in "container creating"

Expected results:
Pod goes running

Additional info:

Comment 6 errata-xmlrpc 2021-10-12 06:01:19 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.8.14 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.

https://access.redhat.com/errata/RHBA-2021:3682