-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.12, 4.17, 4.18, 4.19, 4.20, 4.21
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
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:
{ fail [github.com/openshift/origin/test/extended/quota/resourcequota.go:72]: Unexpected error:
<*errors.errorString | 0xc0022ebf50>:
timed out waiting for the condition: unexpected current total usage: actual: v1.ResourceList{"openshift.io/imagestreams":resource.Quantity{i:resource.int64Amount{value:0, scale:0}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:"0", Format:"DecimalSI"}}, expected: v1.ResourceList{"openshift.io/imagestreams":resource.Quantity{i:resource.int64Amount{value:1, scale:0}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:"1", Format:"DecimalSI"}}
{
s: "timed out waiting for the condition: unexpected current total usage: actual: v1.ResourceList{\"openshift.io/imagestreams\":resource.Quantity{i:resource.int64Amount{value:0, scale:0}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:\"0\", Format:\"DecimalSI\"}}, expected: v1.ResourceList{\"openshift.io/imagestreams\":resource.Quantity{i:resource.int64Amount{value:1, scale:0}, d:resource.infDecAmount{Dec:(*inf.Dec)(nil)}, s:\"1\", Format:\"DecimalSI\"}}",
}
occurred}
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.12, 4.17, 4.18, 4.19, 4.20, and 4.21 CI jobs.
How reproducible
Presently, search.ci shows the following stats for the past two days:
pull-ci-openshift-origin-main-e2e-vsphere-ovn (all) - 57 runs, 23% failed, 8% of failures match = 2% impact openshift-kubernetes-2484-nightly-4.21-e2e-aws-ovn-fips (all) - 4 runs, 50% failed, 50% of failures match = 25% impact periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-upgrade (all) - 85 runs, 33% failed, 7% of failures match = 2% impact pull-ci-openshift-origin-main-e2e-gcp-ovn (all) - 60 runs, 38% failed, 4% of failures match = 2% impact periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade (all) - 71 runs, 28% failed, 5% of failures match = 1% impact periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips (all) - 70 runs, 80% failed, 2% of failures match = 1% impact periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade (all) - 86 runs, 47% failed, 5% of failures match = 2% impact periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview (all) - 10 runs, 30% failed, 33% of failures match = 10% impact periodic-ci-openshift-multiarch-master-nightly-4.20-ocp-e2e-aws-ovn-sno-multi-a-a (all) - 6 runs, 17% failed, 100% of failures match = 17% impact openshift-kubernetes-2484-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade (all) - 50 runs, 22% failed, 9% of failures match = 2% impact openshift-kubernetes-2484-nightly-4.21-e2e-aws-ovn-upi (all) - 4 runs, 25% failed, 100% of failures match = 25% impact periodic-ci-openshift-release-master-nightly-4.20-e2e-vsphere-ovn-upi (all) - 6 runs, 50% failed, 33% of failures match = 17% impact periodic-ci-openshift-release-master-nightly-4.20-e2e-vsphere-ovn-techpreview (all) - 6 runs, 33% failed, 50% of failures match = 17% impact periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade (all) - 87 runs, 39% failed, 3% of failures match = 1% 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%2Fquota%2Fresourcequota%5C.go%3A72%5C%5D%3A+Unexpected+error%3A&maxAge=48h&context=1&type=bug%2Bissue%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
Actual results
The test fails or flakes.
Expected results
The test passes.
Additional info
Most of the failures that I found with search.ci with flakes. That is, the test failed on the first try and passed on retry.
