-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.14
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem
CI is flaky because of test failures of the [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 test, such as the following:
{ fail [github.com/openshift/origin/test/extended/networking/egressip.go:798]: Timed out after 180.003s.
Expected
<bool>: false
to be true
Ginkgo exit error 1: exit with code 1}
This particular failure comes from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-ingress-operator/924/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-serial/1671484138487549952. Search.ci has other similar failures.
Version-Release number of selected component (if applicable)
I have seen this in 4.14 CI jobs.
How reproducible
Presently, search.ci shows the following stats for the past two days:
Found in 0.16% of runs (0.85% of failures) across 42969 total runs and 4564 jobs (19.27% failed) pull-ci-openshift-cluster-etcd-operator-master-e2e-aws-ovn-serial (all) - 3 runs, 100% failed, 67% of failures match = 67% impact pull-ci-openshift-cluster-kube-apiserver-operator-master-e2e-aws-ovn-serial (all) - 13 runs, 69% failed, 56% of failures match = 38% impact pull-ci-openshift-oc-master-e2e-aws-ovn-serial (all) - 13 runs, 92% failed, 33% of failures match = 31% impact periodic-ci-openshift-release-master-nightly-4.14-e2e-aws-ovn-serial (all) - 2 runs, 100% failed, 100% of failures match = 100% impact pull-ci-openshift-origin-master-e2e-aws-ovn-serial (all) - 14 runs, 79% failed, 100% of failures match = 79% impact pull-ci-operator-framework-operator-marketplace-master-e2e-aws-ovn-serial (all) - 4 runs, 100% failed, 50% of failures match = 50% impact periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.14-e2e-openstack-ovn-serial (all) - 2 runs, 100% failed, 50% of failures match = 50% impact pull-ci-openshift-cluster-api-provider-aws-master-e2e-aws-serial (all) - 3 runs, 100% failed, 100% of failures match = 100% impact pull-ci-openshift-cluster-control-plane-machine-set-operator-main-e2e-aws-ovn-serial (all) - 4 runs, 50% failed, 50% of failures match = 25% impact pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-serial (all) - 9 runs, 78% failed, 86% of failures match = 67% impact rehearse-40411-pull-ci-openshift-cloud-network-config-controller-master-e2e-aws--ovn-serial (all) - 2 runs, 100% failed, 100% of failures match = 100% impact pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn-serial (all) - 2 runs, 100% failed, 100% of failures match = 100% impact periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-aws-ovn-arm64-techpreview-serial (all) - 10 runs, 70% failed, 71% of failures match = 50% impact periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-serial-aws-arm64 (all) - 10 runs, 60% failed, 83% of failures match = 50% impact pull-ci-openshift-cluster-kube-scheduler-operator-master-e2e-aws-ovn-serial (all) - 1 runs, 100% failed, 100% of failures match = 100% impact pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-serial (all) - 15 runs, 87% failed, 38% of failures match = 33% impact pull-ci-openshift-kubernetes-master-e2e-aws-ovn-serial (all) - 7 runs, 100% failed, 57% of failures match = 57% impact pull-ci-openshift-cluster-capi-operator-main-e2e-aws-ovn-serial (all) - 8 runs, 75% failed, 50% of failures match = 38% impact pull-ci-openshift-openshift-apiserver-master-e2e-aws-ovn-serial (all) - 2 runs, 50% failed, 100% of failures match = 50% impact pull-ci-openshift-etcd-openshift-4.14-e2e-aws-ovn-serial (all) - 4 runs, 100% failed, 100% of failures match = 100% impact periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance-serial (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
Steps to Reproduce
Actual results
CI fails.
Expected results
CI passes, or fails on some other test failure.
Additional info
In the search.ci results, the failures mostly appear to be in aws jobs, with the exception of one failure of the periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.14-e2e-openstack-ovn-serial job. The failures appear to be in ovn jobs, with the exception of several failures of the pull-ci-openshift-cluster-api-provider-aws-master-e2e-aws-serial job. I only checked the past 2 days because search.ci failed to load with a longer time horizon.
