Bug 1905109

Summary:	[sig-arch][Early] Managed cluster should start all core operators openshift-monitoring/cluster-monitoring-operator
Product:	OpenShift Container Platform	Reporter:	Scott Dodson <sdodson>
Component:	Monitoring	Assignee:	Sergiusz Urbaniak <surbania>
Status:	CLOSED DUPLICATE	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	alegrand, anpicker, dcbw, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	[sig-arch][Early] Managed cluster should start all core operators
Last Closed:	2020-12-08 07:47:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Scott Dodson 2020-12-07 14:36:29 UTC

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

Comment 1 Dan Williams 2020-12-07 15:02:56 UTC

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

Comment 2 Scott Dodson 2020-12-07 17:17:10 UTC

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

Comment 3 Sergiusz Urbaniak 2020-12-08 07:47:38 UTC

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 ***