-
Bug
-
Resolution: Unresolved
-
Critical
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-61135. The following is the description of the original issue:
—
Nightly payloads began permafailing with https://amd64.ocp.releases.ci.openshift.org/releasestream/4.20.0-0.nightly/release/4.20.0-0.nightly-2025-09-01-203437 on the periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-sts-ovn job.
[sig-arch][Early] Managed cluster should [apigroup:config.openshift.io] start all core operators [Skipped:Disconnected] [Suite:openshift/conformance/parallel] expand_less
Run #0: Failed expand_less 0s
{ fail [github.com/openshift/origin/test/extended/operators/operators.go:139]: Some cluster operators are not ready: monitoring (Upgradeable=False InvalidConfiguration: configuration in the "openshift-monitoring/cluster-monitoring-config" ConfigMap is invalid and should be fixed: k8sPrometheusAdapter is deprecated and usage should be removed, use metricsServer instead)}
Which appears to be from this PR: https://github.com/openshift/cluster-monitoring-operator/pull/2651
Per our policy: https://github.com/openshift/enhancements/blob/master/enhancements/release/improving-ci-signal.md#quick-revert
We need to revert to get payloads stabilized. Coordination with ROSA folks will be necessary to roll this out. See #wg-hcm-ocp-release-enablement
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
