test: [sig-arch][Early] Managed cluster should start all core operators 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-arch%5C%5D%5C%5BEarly%5C%5D+Managed+cluster+should+start+all+core+operators https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/407/pull-ci-openshift-kubernetes-release-4.6-e2e-aws/1335915553193201664 Fail [github.com/openshift/origin/test/extended/operators/cluster.go:151]: Expected <[]string | len:1, cap:1>: [ "Pod openshift-monitoring/cluster-monitoring-operator-5d4d547954-v5kwk was pending entire time: unknown error", ] to be empty
Also: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/353/pull-ci-openshift-ovn-kubernetes-release-4.6-e2e-vsphere-ovn/1335907988895961088 Dec 7 12:26:45.296: FAIL: ClusterVersion Failing=True: WorkloadNotAvailable: deployment openshift-monitoring/cluster-monitoring-operator is not available MinimumReplicasUnavailable (Deployment does not have minimum availability.) or progressing ProgressDeadlineExceeded (ReplicaSet "cluster-monitoring-operator-58b59c4cd7" has timed out progressing.) CMO logs: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/353/pull-ci-openshift-ovn-kubernetes-release-4.6-e2e-vsphere-ovn/1335907988895961088/artifacts/e2e-vsphere-ovn/gather-extra/pods/openshift-monitoring_cluster-monitoring-operator-58b59c4cd7-2rpt9_cluster-monitoring-operator.log
Bug 1904538 is very similar, I'm not sure why Sippy didn't indicate there was a bug for this already but I'll leave it up to the assigned team to decide if this is a dupe
error logs indicate this is the same issue as 1904538, hence closing out as a duplicate. *** This bug has been marked as a duplicate of bug 1904538 ***