Bug 2089937

Summary: New EgressIP upstream tests are broken on Azure ovn serial
Product: OpenShift Container Platform Reporter: Devan Goodwin <dgoodwin>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED DUPLICATE Docs Contact:
Severity: low    
Priority: unspecified CC: akaris, ffernand
Version: 4.11   
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-05-25 13:39:07 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 Devan Goodwin 2022-05-24 18:24:15 UTC 
Description of problem:

New tests are permafailing on Azure:

https://sippy.dptools.openshift.org/sippy-ng/tests/4.11/analysis?test=[sig-network][Feature:EgressIP]%20[external-targets]%20pods%20should%20keep%20the%20assigned%20EgressIPs%20when%20being%20rescheduled%20to%20another%20node%20[Serial]%20[Suite:openshift/conformance/serial]

In the nurp panel we see this is only affecting Azure ovn. Looking at the failures seems to always show:

{  fail [github.com/openshift/origin/test/extended/networking/egressip.go:690]: Timed out after 64.026s.
Expected
    <bool>: false
to be true}


Example: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.11-e2e-azure-serial/1528805602447331328

Seems to affect two tests:

: [sig-network][Feature:EgressIP] [external-targets] pods should keep the assigned EgressIPs when being rescheduled to another node [Serial] [Suite:openshift/conformance/serial] 

: [sig-network][Feature:EgressIP] [external-targets] EgressIPs can be assigned automatically [Skipped:Network/OVNKubernetes] [Serial] [Suite:openshift/conformance/serial]
Comment 1 Andreas Karis 2022-05-25 13:39:07 UTC 

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