+++ This bug was initially created as a clone of Bug #1989100 +++ job: periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn is failing frequently in CI, see testgrid results: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.9-informing#periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn Here is a test run that had 8 errors only: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn/1421446191245168640 In particular, these two tests seem to be failing most of the time: * [sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2 [Suite:openshift/conformance/parallel] [Suite:k8s] * [sig-auth][Feature:OpenShiftAuthorization][Serial] authorization TestAuthorizationResourceAccessReview should succeed [Suite:openshift/conformance/serial] --- Additional comment from Pierre Prinetti on 2021-10-20 16:46:12 BST --- From the bug triage meeting: we unset TRIAGED so that the pre-triager can assess the state of the periodic and update the status here. --- Additional comment from Matthew Booth on 2021-10-25 14:16:03 BST --- There are 3 tests which are failing 100% of the time: openshift-tests.[sig-auth][Feature:OpenShiftAuthorization][Serial] authorization TestAuthorizationResourceAccessReview should succeed [Suite:openshift/conformance/serial] openshift-tests.[sig-network-edge][Feature:Idling] Unidling should handle many TCP connections by possibly dropping those over a certain bound [Serial] [Suite:openshift/conformance/serial] openshift-tests.[sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2 [Suite:openshift/conformance/parallel] [Suite:k8s]
origin branch release-4.9 has not vendored the upstream change which reduces iperf2BaselineBandwidthMegabytesPerSecond from 90 to to, which is why this succeeds in 4.10 but not 4.9. I don't know how likely this is to happen. Perhaps we should skip this test on <4.10?
@Martin has already posted a fix for this, which backports the upstream change. We need to get it to land.
*** This bug has been marked as a duplicate of bug 2010225 ***