+++ This bug was initially created as a clone of Bug #1893201 +++
The e2e-operator test frequently fails on a prometheus timeout:
--- FAIL: TestMetricsAccessible (30.57s)
scheduler_test.go:317: prometheus returned unexpected results: timed out waiting for the condition
FAIL github.com/openshift/cluster-kube-scheduler-operator/test/e2e 35.059s
We have tried extending the timeout for this test (https://github.com/openshift/cluster-kube-scheduler-operator/pull/299). It seems to fail for many runs before eventually passing
--- Additional comment from Mike Dame on 2020-10-30 14:33:45 UTC ---
Going to try backporting the change from #299 to release-4.5, where we're currently seeing the problem.
For QE, this bug should be verifiable by confirming that this test hasn't had any recent failures in CI
Verified by looking at the link below and did not see any failure in last 24 hours, based on that moving bug to verified state.
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.5.20 bug fix and golang 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.