test: [sig-instrumentation] Prometheus when installed on the cluster should start and expose a secured proxy and unsecured metrics is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-instrumentation%5C%5D+Prometheus+when+installed+on+the+cluster+should+start+and+expose+a+secured+proxy+and+unsecured+metrics specific job here: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.6/1291710582575075328 Sippy is reporting this test as failing 10% of the time. It appears to be failing without non-prometheus tests failing. I often see it in concert with test: [sig-instrumentation] Prometheus when installed on the cluster should have important platform topology metrics [Suite:openshift/conformance/parallel] fail [github.com/openshift/origin/test/extended/prometheus/prometheus.go:253]: possibly some services didn't register ServiceMonitors to allow metrics collection Unexpected error: <*errors.errorString | 0xc0002a08a0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred
Thanks a lot for the catch, this is a great investigation source. We identified the issue already and found that prometheus-operator can miss reconciling underlying CRDs. Closing out as duplicate to reduce BZ noise. *** This bug has been marked as a duplicate of bug 1856189 ***