Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-62930

CI fails or flakes on "[sig-network][Feature:EgressFirewall] when using openshift ovn-kubernetes should ensure egressfirewall is created"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.20, 4.21
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem

      CI is flaky because of test failures such as the following:

        STEP: Creating a kubernetes client @ 10/09/25 22:38:48.165
      I1009 22:38:48.258710 310436 client.go:288] configPath is now "/tmp/configfile1998074946"
      I1009 22:38:48.258751 310436 client.go:363] The user is now "e2e-test-egress-firewall-e2e-752t9-user"
      I1009 22:38:48.258760 310436 client.go:365] Creating project "e2e-test-egress-firewall-e2e-752t9"
      I1009 22:38:48.335962 310436 client.go:373] Waiting on permissions in project "e2e-test-egress-firewall-e2e-752t9" ...
      I1009 22:38:48.408007 310436 client.go:402] DeploymentConfig capability is enabled, adding 'deployer' SA to the list of default SAs
      I1009 22:38:48.413581 310436 client.go:417] Waiting for ServiceAccount "default" to be provisioned...
      I1009 22:38:48.532776 310436 client.go:417] Waiting for ServiceAccount "builder" to be provisioned...
      I1009 22:38:48.655246 310436 client.go:417] Waiting for ServiceAccount "deployer" to be provisioned...
      I1009 22:38:48.790140 310436 client.go:427] Waiting for RoleBinding "system:image-pullers" to be provisioned...
      I1009 22:38:48.815593 310436 client.go:427] Waiting for RoleBinding "system:image-builders" to be provisioned...
      I1009 22:38:48.825030 310436 client.go:427] Waiting for RoleBinding "system:deployers" to be provisioned...
      I1009 22:38:49.102303 310436 client.go:460] Project "e2e-test-egress-firewall-e2e-752t9" has been fully provisioned.
        STEP: Creating a kubernetes client @ 10/09/25 22:38:49.102
      I1009 22:38:49.212511 310436 resource_usage_gatherer.go:392] Can't find any pods in namespace kube-system to grab metrics from
      I1009 22:38:49.216703 310436 resource_usage_gatherer.go:392] Can't find any pods in namespace kube-system to grab metrics from
      I1009 22:38:49.220504 310436 resource_usage_gatherer.go:392] Can't find any pods in namespace kube-system to grab metrics from
      I1009 22:38:49.224644 310436 resource_usage_gatherer.go:392] Can't find any pods in namespace kube-system to grab metrics from
      I1009 22:38:49.230031 310436 resource_usage_gatherer.go:392] Can't find any pods in namespace kube-system to grab metrics from
      I1009 22:38:49.235812 310436 resource_usage_gatherer.go:392] Can't find any pods in namespace kube-system to grab metrics from
      I1009 22:38:49.235935 310436 resource_usage_gatherer.go:342] Closing worker for ci-op-zm9swcry-4cd5c-vpqfk-worker-0-wwqf9
      I1009 22:38:49.235977 310436 resource_usage_gatherer.go:342] Closing worker for ci-op-zm9swcry-4cd5c-vpqfk-worker-0-9fz9w
      I1009 22:38:49.235967 310436 resource_usage_gatherer.go:342] Closing worker for ci-op-zm9swcry-4cd5c-vpqfk-master-2
        STEP: Creating a kubernetes client @ 10/09/25 22:38:49.235
      I1009 22:38:49.236022 310436 resource_usage_gatherer.go:342] Closing worker for ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5
      I1009 22:38:49.236079 310436 resource_usage_gatherer.go:342] Closing worker for ci-op-zm9swcry-4cd5c-vpqfk-master-1
      I1009 22:38:49.291217 310436 resource_usage_gatherer.go:336] Closing worker for ci-op-zm9swcry-4cd5c-vpqfk-master-0
      I1009 22:38:49.340464 310436 client.go:288] configPath is now "/tmp/configfile204984605"
      I1009 22:38:49.340493 310436 client.go:363] The user is now "e2e-test-no-egress-firewall-e2e-2jhbw-user"
      I1009 22:38:49.340503 310436 client.go:365] Creating project "e2e-test-no-egress-firewall-e2e-2jhbw"
      I1009 22:38:49.415701 310436 client.go:373] Waiting on permissions in project "e2e-test-no-egress-firewall-e2e-2jhbw" ...
      I1009 22:38:49.482233 310436 client.go:402] DeploymentConfig capability is enabled, adding 'deployer' SA to the list of default SAs
      I1009 22:38:49.490241 310436 client.go:417] Waiting for ServiceAccount "default" to be provisioned...
      I1009 22:38:49.601765 310436 client.go:417] Waiting for ServiceAccount "builder" to be provisioned...
      I1009 22:38:49.717870 310436 client.go:417] Waiting for ServiceAccount "deployer" to be provisioned...
      I1009 22:38:49.833596 310436 client.go:427] Waiting for RoleBinding "system:image-pullers" to be provisioned...
      I1009 22:38:49.840872 310436 client.go:427] Waiting for RoleBinding "system:image-builders" to be provisioned...
      I1009 22:38:49.850523 310436 client.go:427] Waiting for RoleBinding "system:deployers" to be provisioned...
      I1009 22:38:50.117826 310436 client.go:460] Project "e2e-test-no-egress-firewall-e2e-2jhbw" has been fully provisioned.
        STEP: creating test pod @ 10/09/25 22:38:50.244
      I1009 22:38:50.266031 310436 util.go:383] Using ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5 and ci-op-zm9swcry-4cd5c-vpqfk-worker-0-9fz9w for test ([ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5 ci-op-zm9swcry-4cd5c-vpqfk-worker-0-9fz9w ci-op-zm9swcry-4cd5c-vpqfk-worker-0-wwqf9] out of [ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5 ci-op-zm9swcry-4cd5c-vpqfk-worker-0-9fz9w ci-op-zm9swcry-4cd5c-vpqfk-worker-0-wwqf9])
        STEP: executing a successful access to external internet @ 10/09/25 22:38:54.316
      I1009 22:38:54.316753 310436 client.go:1023] Running 'oc --namespace=e2e-test-egress-firewall-e2e-752t9 --kubeconfig=/tmp/configfile1998074946 exec egressfirewall -- curl -q -s -I -m5 http://www.google.com:80'
        STEP: creating an egressfirewall object @ 10/09/25 22:38:55.055
        STEP: calling oc create -f /tmp/fixture-testdata-dir2959316689/test/extended/testdata/egress-firewall/ovnk-egressfirewall-test.yaml @ 10/09/25 22:38:55.055
      I1009 22:38:55.055804 310436 client.go:1023] Running 'oc --namespace=e2e-test-egress-firewall-e2e-752t9 --kubeconfig=/tmp/kubeconfig-3762687593 create -f /tmp/fixture-testdata-dir2959316689/test/extended/testdata/egress-firewall/ovnk-egressfirewall-test.yaml'
      egressfirewall.k8s.ovn.org/default created
        STEP: sending traffic that matches allow cidr rule @ 10/09/25 22:38:55.236
      I1009 22:38:55.236888 310436 client.go:1023] Running 'oc --namespace=e2e-test-egress-firewall-e2e-752t9 --kubeconfig=/tmp/configfile1998074946 exec egressfirewall -- ping -c 1 8.8.8.8'
        STEP: sending traffic that does not match allow cidr rule @ 10/09/25 22:38:55.656
      I1009 22:38:55.656989 310436 client.go:1023] Running 'oc --namespace=e2e-test-egress-firewall-e2e-752t9 --kubeconfig=/tmp/configfile1998074946 exec egressfirewall -- ping -c 1 1.1.1.1'
        [FAILED] in [It] - github.com/openshift/origin/test/extended/networking/egress_firewall.go:139 @ 10/09/25 22:38:56.003
        STEP: Collecting events from namespace "e2e-test-egress-firewall-e2e-752t9". @ 10/09/25 22:38:56.003
        STEP: Found 4 events. @ 10/09/25 22:38:56.013
      I1009 22:38:56.013877 310436 dump.go:53] At 2025-10-09 22:38:52 +0000 UTC - event for egressfirewall: {multus } AddedInterface: Add eth0 [10.131.1.149/23] from ovn-kubernetes
      I1009 22:38:56.013895 310436 dump.go:53] At 2025-10-09 22:38:52 +0000 UTC - event for egressfirewall: {kubelet ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5} Pulled: Container image "quay.io/openshift/community-e2e-images:e2e-1-registry-k8s-io-e2e-test-images-agnhost-2-53-S5hiptYgC5MyFXZH" already present on machine
      I1009 22:38:56.013905 310436 dump.go:53] At 2025-10-09 22:38:52 +0000 UTC - event for egressfirewall: {kubelet ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5} Created: Created container: egressfirewall-container
      I1009 22:38:56.013914 310436 dump.go:53] At 2025-10-09 22:38:52 +0000 UTC - event for egressfirewall: {kubelet ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5} Started: Started container egressfirewall-container
      I1009 22:38:56.037671 310436 resource.go:168] POD             NODE                                       PHASE    GRACE  CONDITIONS
      I1009 22:38:56.037752 310436 resource.go:175] egressfirewall  ci-op-zm9swcry-4cd5c-vpqfk-worker-0-25np5  Running         [{PodReadyToStartContainers 0 True 0001-01-01 00:00:00 +0000 UTC 2025-10-09 22:38:52 +0000 UTC  } {Initialized 0 True 0001-01-01 00:00:00 +0000 UTC 2025-10-09 22:38:50 +0000 UTC  } {Ready 0 True 0001-01-01 00:00:00 +0000 UTC 2025-10-09 22:38:52 +0000 UTC  } {ContainersReady 0 True 0001-01-01 00:00:00 +0000 UTC 2025-10-09 22:38:52 +0000 UTC  } {PodScheduled 0 True 0001-01-01 00:00:00 +0000 UTC 2025-10-09 22:38:50 +0000 UTC  }]
      I1009 22:38:56.037763 310436 resource.go:178] 
      I1009 22:38:56.124673 310436 dump.go:81] skipping dumping cluster info - cluster too large
      I1009 22:38:56.148109 310436 client.go:676] Deleted {user.openshift.io/v1, Resource=users  e2e-test-egress-firewall-e2e-752t9-user}, err: <nil>
      I1009 22:38:56.173323 310436 client.go:676] Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-egress-firewall-e2e-752t9}, err: <nil>
      I1009 22:38:56.200634 310436 client.go:676] Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~BJtmBr3LgufvE0jEj3-zqg4J0_lTIZ4UWg2-2p8KJmQ}, err: <nil>
        STEP: Collecting events from namespace "e2e-test-no-egress-firewall-e2e-2jhbw". @ 10/09/25 22:38:56.2
        STEP: Found 0 events. @ 10/09/25 22:38:56.216
      I1009 22:38:56.232164 310436 resource.go:168] POD  NODE  PHASE  GRACE  CONDITIONS
      I1009 22:38:56.232188 310436 resource.go:178] 
      I1009 22:38:56.248725 310436 dump.go:81] skipping dumping cluster info - cluster too large
      I1009 22:38:56.266268 310436 client.go:676] Deleted {user.openshift.io/v1, Resource=users  e2e-test-no-egress-firewall-e2e-2jhbw-user}, err: <nil>
      I1009 22:38:56.282278 310436 client.go:676] Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-no-egress-firewall-e2e-2jhbw}, err: <nil>
      I1009 22:38:56.310058 310436 client.go:676] Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~GXRpeNZGi5B8OXdUy_3gP32fJ5WB5ojXw3COtNODI_U}, err: <nil>
        STEP: Destroying namespace "e2e-test-no-egress-firewall-e2e-2jhbw" for this suite. @ 10/09/25 22:38:56.31
        STEP: Collecting resource usage data @ 10/09/25 22:38:56.323
      I1009 22:38:56.324015 310436 resource_usage_gatherer.go:518] Closed stop channel. Waiting for 6 workers
      I1009 22:38:56.324037 310436 resource_usage_gatherer.go:526] Waitgroup finished.
        STEP: dump namespace information after failure @ 10/09/25 22:38:56.324
      I1009 22:38:56.324147 310436 framework.go:310] Printing summary: ResourceUsageSummary
      I1009 22:38:56.324161 310436 framework.go:334] Writing to /logs/artifacts/junit/ResourceUsageSummary_mgmt-framework_2025-10-09T22:38:56Z.json
        STEP: Destroying namespace "e2e-test-egress-firewall-e2e-752t9" for this suite. @ 10/09/25 22:38:56.324
      
      fail [github.com/openshift/origin/test/extended/networking/egress_firewall.go:139]: Expected an error to have occurred.  Got:
          <nil>: nil
      

      This particular failure comes from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29900/pull-ci-openshift-origin-main-e2e-vsphere-ovn/1976388824435003392. Search.ci has other similar failures.

      Version-Release number of selected component (if applicable)

      I have seen this in 4.20 and 4.21 CI jobs.

      How reproducible

      Presently, search.ci shows the following stats for the past two days:

      periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ovn-two-node-fencing-dualstack-techpreview (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
      openshift-kubernetes-2484-ci-4.21-e2e-gcp-ovn-techpreview (all) - 4 runs, 50% failed, 100% of failures match = 50% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-gcp-ovn-runc (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
      openshift-kubernetes-2484-periodics-e2e-aws-ovn-conformance (all) - 50 runs, 32% failed, 31% of failures match = 10% impact
      pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi (all) - 63 runs, 40% failed, 52% of failures match = 21% impact
      openshift-kubernetes-2484-nightly-4.21-e2e-vsphere-ovn (all) - 4 runs, 25% failed, 100% of failures match = 25% impact
      periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade (all) - 80 runs, 28% failed, 27% of failures match = 8% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips (all) - 76 runs, 80% failed, 8% of failures match = 7% impact
      periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-upgrade (all) - 85 runs, 33% failed, 96% of failures match = 32% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-techpreview (all) - 7 runs, 14% failed, 400% of failures match = 57% impact
      pull-ci-openshift-origin-main-e2e-aws-ovn-fips (all) - 62 runs, 34% failed, 24% of failures match = 8% impact
      periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview (all) - 7 runs, 57% failed, 50% of failures match = 29% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-techpreview (all) - 7 runs, 29% failed, 250% of failures match = 71% impact
      pull-ci-openshift-origin-main-e2e-gcp-ovn (all) - 63 runs, 44% failed, 57% of failures match = 25% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack-bgp-local-gw (all) - 17 runs, 53% failed, 33% of failures match = 18% impact
      periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance (all) - 72 runs, 14% failed, 130% of failures match = 18% impact
      pull-ci-openshift-origin-main-e2e-vsphere-ovn (all) - 60 runs, 32% failed, 47% of failures match = 15% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack-bgp (all) - 18 runs, 50% failed, 56% of failures match = 28% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack (all) - 13 runs, 15% failed, 150% of failures match = 23% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn (all) - 12 runs, 8% failed, 300% of failures match = 25% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-local-to-shared-gateway-mode-migration (all) - 13 runs, 8% failed, 200% of failures match = 15% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-hypershift (all) - 15 runs, 40% failed, 33% of failures match = 13% impact
      openshift-kubernetes-2484-ci-4.21-e2e-gcp-ovn-upgrade (all) - 53 runs, 36% failed, 32% of failures match = 11% impact
      openshift-kubernetes-2484-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade (all) - 54 runs, 31% failed, 24% of failures match = 7% impact
      pull-ci-openshift-machine-config-operator-main-okd-scos-e2e-aws-ovn (all) - 5 runs, 60% failed, 33% of failures match = 20% impact
      openshift-origin-30360-periodics-e2e-aws-ovn-conformance (all) - 10 runs, 100% failed, 10% of failures match = 10% impact
      pull-ci-openshift-cluster-etcd-operator-main-okd-scos-e2e-aws-ovn (all) - 12 runs, 50% failed, 17% of failures match = 8% impact
      pull-ci-openshift-api-master-e2e-gcp (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
      periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade (all) - 87 runs, 39% failed, 35% of failures match = 14% impact
      periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-upgrade-out-of-change (all) - 7 runs, 57% failed, 75% of failures match = 43% impact
      pull-ci-openshift-cluster-etcd-operator-main-e2e-agnostic-ovn (all) - 13 runs, 15% failed, 150% of failures match = 23% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-dualstack (all) - 7 runs, 43% failed, 33% of failures match = 14% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-dualstack-techpreview (all) - 7 runs, 29% failed, 100% of failures match = 29% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-upgrade-local-gateway (all) - 13 runs, 15% failed, 50% of failures match = 8% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview (all) - 14 runs, 50% failed, 43% of failures match = 21% impact
      periodic-ci-openshift-multiarch-master-nightly-4.21-ocp-e2e-upgrade-aws-ovn-multi-a-a (all) - 6 runs, 33% failed, 50% of failures match = 17% impact
      pull-ci-openshift-image-customization-controller-main-e2e-metal-ipi-virtualmedia (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
      pull-ci-openshift-cluster-api-master-e2e-aws-ovn-techpreview (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
      pull-ci-openshift-cluster-version-operator-main-e2e-aws-ovn-techpreview (all) - 10 runs, 50% failed, 60% of failures match = 30% impact
      pull-ci-openshift-cluster-monitoring-operator-main-e2e-aws-ovn (all) - 17 runs, 35% failed, 50% of failures match = 18% impact
      pull-ci-openshift-api-master-e2e-aws-ovn-techpreview (all) - 5 runs, 60% failed, 67% of failures match = 40% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-upgrade (all) - 12 runs, 8% failed, 100% of failures match = 8% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-shared-to-local-gateway-mode-migration (all) - 12 runs, 8% failed, 100% of failures match = 8% impact
      pull-ci-openshift-machine-api-provider-openstack-main-e2e-openstack (all) - 3 runs, 100% failed, 33% of failures match = 33% impact
      openshift-ovn-kubernetes-2790-nightly-4.21-e2e-aws-ovn-upgrade-fips (all) - 40 runs, 68% failed, 11% of failures match = 8% impact
      pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance (all) - 3 runs, 67% failed, 50% of failures match = 33% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn (all) - 12 runs, 8% failed, 100% of failures match = 8% impact
      openshift-ovn-kubernetes-2790-ci-4.21-e2e-gcp-ovn-upgrade (all) - 40 runs, 73% failed, 14% of failures match = 10% impact
      openshift-ovn-kubernetes-2790-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade (all) - 40 runs, 57% failed, 17% of failures match = 10% impact
      openshift-ovn-kubernetes-2790-ci-4.21-e2e-aws-ovn-techpreview (all) - 4 runs, 50% failed, 50% of failures match = 25% impact
      openshift-ovn-kubernetes-2790-periodics-e2e-aws-ovn-conformance (all) - 40 runs, 38% failed, 27% of failures match = 10% impact
      pull-ci-openshift-origin-main-e2e-openstack-ovn (all) - 4 runs, 100% failed, 25% of failures match = 25% impact
      pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws (all) - 28 runs, 11% failed, 100% of failures match = 11% impact
      pull-ci-openshift-cluster-monitoring-operator-main-e2e-hypershift-conformance (all) - 14 runs, 14% failed, 100% of failures match = 14% impact
      periodic-ci-openshift-cluster-network-operator-release-4.21-e2e-aws-ovn-clusternetwork-cidr-expansion (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
      openshift-kubernetes-2484-nightly-4.21-e2e-aws-ovn-upgrade-fips (all) - 41 runs, 37% failed, 33% of failures match = 12% impact
      openshift-kubernetes-2484-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade (all) - 46 runs, 22% failed, 30% of failures match = 7% impact
      pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws-techpreview (all) - 6 runs, 83% failed, 20% of failures match = 17% impact
      pull-ci-openshift-cluster-monitoring-operator-main-e2e-aws-ovn-techpreview (all) - 16 runs, 25% failed, 50% of failures match = 13% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-runc (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
      periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn (all) - 7 runs, 29% failed, 150% of failures match = 43% impact
      periodic-ci-openshift-cloud-credential-operator-release-4.22-periodics-e2e-gcp-manual-oidc (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
      openshift-kubernetes-2484-ci-4.21-e2e-aws-ovn-techpreview (all) - 5 runs, 20% failed, 200% of failures match = 40% impact
      pull-ci-openshift-installer-main-e2e-gcp-ovn-xpn (all) - 2 runs, 50% failed, 200% of failures match = 100% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-rosa-sts-ovn (all) - 12 runs, 75% failed, 11% of failures match = 8% impact
      periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade (all) - 7 runs, 43% failed, 67% of failures match = 29% impact
      pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn (all) - 6 runs, 17% failed, 100% of failures match = 17% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-osd-ccs-gcp (all) - 9 runs, 100% failed, 22% of failures match = 22% impact
      openshift-kubernetes-2484-nightly-4.21-e2e-vsphere-ovn-upi (all) - 4 runs, 50% failed, 50% of failures match = 25% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-upi (all) - 7 runs, 14% failed, 200% of failures match = 29% impact
      periodic-ci-openshift-multiarch-master-nightly-4.21-upgrade-from-stable-4.20-ocp-e2e-upgrade-aws-ovn-multi-a-a (all) - 6 runs, 33% failed, 50% of failures match = 17% impact
      pull-ci-openshift-kubernetes-master-e2e-gcp (all) - 5 runs, 80% failed, 25% of failures match = 20% impact
      pull-ci-openshift-installer-main-e2e-openstack-ovn (all) - 6 runs, 100% failed, 17% of failures match = 17% impact
      periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-openstack-aws-conformance (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
      pull-ci-openshift-service-ca-operator-main-e2e-aws (all) - 5 runs, 60% failed, 33% of failures match = 20% impact
      periodic-ci-openshift-release-master-okd-scos-4.21-e2e-aws-ovn-techpreview (all) - 10 runs, 90% failed, 11% of failures match = 10% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-upi-multi-vcenter (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
      pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-local-gateway (all) - 12 runs, 17% failed, 50% of failures match = 8% impact
      pull-ci-openshift-cluster-capi-operator-main-e2e-aws-ovn-techpreview (all) - 5 runs, 40% failed, 150% of failures match = 60% impact
      pull-ci-openshift-monitoring-plugin-main-e2e-aws-ovn (all) - 18 runs, 28% failed, 20% of failures match = 6% impact
      periodic-ci-openshift-multiarch-master-nightly-4.21-ocp-e2e-aws-ovn-techpreview-multi-a-a (all) - 6 runs, 17% failed, 100% of failures match = 17% impact
      pull-ci-openshift-monitoring-plugin-main-okd-scos-e2e-aws-ovn (all) - 18 runs, 44% failed, 13% of failures match = 6% impact
      pull-ci-openshift-kubernetes-master-e2e-aws-ovn-crun (all) - 5 runs, 60% failed, 33% of failures match = 20% impact
      pull-ci-openshift-cluster-capi-operator-main-e2e-openstack-ovn-techpreview (all) - 6 runs, 83% failed, 20% of failures match = 17% impact
      pull-ci-openshift-prometheus-main-e2e-aws-ovn (all) - 3 runs, 67% failed, 50% of failures match = 33% impact
      periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-fips (all) - 7 runs, 14% failed, 100% of failures match = 14% impact
      periodic-ci-openshift-ovn-kubernetes-release-4.21-periodics-e2e-metal-ipi-ovn-dualstack-bgp (all) - 2 runs, 50% failed, 100% of failures match = 50% impact
      periodic-ci-openshift-multiarch-master-nightly-4.21-ocp-e2e-aws-ovn-multi-x-ax (all) - 6 runs, 33% failed, 50% of failures match = 17% impact
      openshift-kubernetes-2484-nightly-4.21-e2e-metal-ipi-ovn-upgrade (all) - 4 runs, 25% failed, 100% of failures match = 25% impact
      

      Steps to Reproduce

      1. Post a PR and have bad luck.
      2. Check search.ci: https://search.dptools.openshift.org/?search=fail+%5C%5Bgithub%5C.com%2Fopenshift%2Forigin%2Ftest%2Fextended%2Fnetworking%2Fegress_firewall%5C.go%3A139%5C%5D%3A+Expected+an+error+to+have+occurred&maxAge=48h&context=1&type=bug%2Bissue%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

      Actual results

      CI fails or flakes on this test.

      Expected results

      The test passes.

      Affected Platforms

      AWS, GCP, metal, OpenStack, vSphere

      Is it an internal CI failure.

      I do not see any failures for sdn jobs.

      Here is another failure, this one for gcp:

      https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30297/pull-ci-openshift-origin-main-e2e-gcp-ovn/1976337495880634368

      Most of the time, the test failure is a flake. That is, it fails on first pass and succeeds on second pass, so it gets marked as a flake in the CI job.

              rh-ee-arsen Arkadeep Sen (Aurko)
              mmasters1@redhat.com Miciah Masters
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: