The test [Serial] [sig-auth][Feature:OAuthServer] [RequestHeaders] [IdP] test RequestHeaders IdP [Suite:openshift/conformance/serial] Has been failing in some recent runs of e2e-aws-serial. See example jobs: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-serial-4.8/1377157189675782144 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial/1377172439477260288 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial/1377257801604141056 Query: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.8-blocking#periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial&sort-by-flakiness= This does not seem to be very consistent so marking as medium priority.
I'm going to increase the severity, based on: $ w3m -dump -cols 200 'https://search.ci.openshift.org/?maxAge=24h&type=junit&search=test+RequestHeaders+IdP' | grep 'fai lures match' | sort periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial (all) - 6 runs, 83% failed, 40% of failures match = 33% impact periodic-ci-openshift-release-master-ci-4.8-e2e-azure-serial (all) - 1 runs, 100% failed, 100% of failures match = 100% impact periodic-ci-openshift-release-master-nightly-4.8-e2e-vsphere-serial (all) - 3 runs, 100% failed, 67% of failures match = 67% impact periodic-ci-openshift-release-master-nightly-4.8-e2e-vsphere-upi-serial (all) - 4 runs, 100% failed, 100% of failures match = 100% impact pull-ci-openshift-cluster-kube-apiserver-operator-master-e2e-aws-serial (all) - 11 runs, 100% failed, 45% of failures match = 45% impact pull-ci-openshift-kubernetes-master-e2e-aws-serial (all) - 8 runs, 75% failed, 67% of failures match = 50% impact pull-ci-openshift-machine-config-operator-master-e2e-aws-serial (all) - 6 runs, 33% failed, 50% of failures match = 17% impact pull-ci-openshift-origin-master-e2e-aws-serial (all) - 78 runs, 97% failed, 7% of failures match = 6% impact release-openshift-ocp-installer-e2e-aws-serial-4.8 (all) - 2 runs, 100% failed, 50% of failures match = 50% impact release-openshift-ocp-installer-e2e-azure-serial-4.8 (all) - 1 runs, 100% failed, 100% of failures match = 100% impact release-openshift-ocp-installer-e2e-gcp-serial-4.8 (all) - 1 runs, 100% failed, 100% of failures match = 100% impact release-openshift-ocp-installer-e2e-openstack-serial-4.8 (all) - 3 runs, 67% failed, 100% of failures match = 67% impact
Made a search https://testgrid.k8s.io/redhat-openshift-ocp-release-4.8-blocking#periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial&sort-by-flakiness, from results, in the past two weeks, only a few failed tests, the reason as below, no longer see the previous error 'timed out waiting for the condition' fail [github.com/openshift/origin/test/extended/oauth/requestheaders.go:204]: unexpected error response status (401) while trying to reach '/oauth/authorize?client_id=openshift-challenging-client&response_type=token' endpoint: HTTP/1.1 401 Unauthorized $ w3m -dump -cols 200 'https://search.ci.openshift.org/?maxAge=24h&type=junit&search=test+RequestHeaders+IdP' | grep 'failures match' | sort periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial (all) - 18 runs, 67% failed, 17% of failures match = 11% impact periodic-ci-openshift-release-master-nightly-4.8-e2e-metal-ipi-serial-ipv4 (all) - 6 runs, 50% failed, 33% of failures match = 17% impact pull-ci-openshift-kubernetes-master-e2e-aws-serial (all) - 17 runs, 18% failed, 33% of failures match = 6% impact pull-ci-openshift-origin-master-e2e-aws-serial (all) - 13 runs, 31% failed, 25% of failures match = 8% impact One better results than before, so move the bug VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438