Bug 2089937 - New EgressIP upstream tests are broken on Azure ovn serial
Summary: New EgressIP upstream tests are broken on Azure ovn serial
Keywords:
Status: CLOSED DUPLICATE of bug 2089276
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 18:24 UTC by Devan Goodwin
Modified: 2022-05-25 13:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-25 13:39:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.