Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-2497

Egress tests failure caused a few nightly jobs to fail in 4.22/4.21/4.20

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • 4.20.0, 4.21, 4.22
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Quite a few jobs in the nightlies are failing with the same Egress tests. This affect nightlies from 4.22, 4.21 and 4.20.

      : [sig-network][Feature:EgressIP][apigroup:operator.openshift.io] [external-targets][apigroup:user.openshift.io][apigroup:security.openshift.io] pods should have the assigned EgressIPs and EgressIPs can be updated [Serial] [Suite:openshift/conformance/serial]
      : [sig-network][Feature:EgressIP][apigroup:operator.openshift.io] [external-targets][apigroup:user.openshift.io][apigroup:security.openshift.io] pods should keep the assigned EgressIPs when being rescheduled to another node [Serial] [Suite:openshift/conformance/serial]
      : [sig-network][Feature:EgressIP][apigroup:operator.openshift.io] [external-targets][apigroup:user.openshift.io][apigroup:security.openshift.io] pods should have the assigned EgressIPs and EgressIPs can be deleted and recreated [Skipped:azure][apigroup:route.openshift.io] [Serial] [Suite:openshift/conformance/serial]
      : [sig-network][Feature:EgressIP][apigroup:operator.openshift.io] [external-targets][apigroup:user.openshift.io][apigroup:security.openshift.io] only pods matched by the pod selector should have the EgressIPs [Serial] [Suite:openshift/conformance/serial]
      

       

      Example payload for 4.22: 4.22.0-0.nightly-2026-01-09-023214

       

      Jobs that failed with Egress tests in that payload:

      aws-ovn-serial-1of2 Failed 

      aws-ovn-techpreview-serial-1of3 Failed 

      aws-ovn-techpreview-serial-2of3 Failed

      aws-ovn-techpreview-serial-3of3 Failed 

       

      All tests failed with the same signature:

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

       

      We recently dealt with another case where golang change with IP address handling that caused some hypershift jobs to fail across 4.22/4.21/4.20. We suspect it might have similar cause here. But we have not found the real reason yet. For reference, hypershift incident is TRT-2492. Relevant slack thread about TRT-2492 is here

       

       

       

       

       

              Unassigned Unassigned
              kenzhang@redhat.com Ken Zhang
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: