Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1721897

Summary: CI: Could not update operatorgroup \"openshift-monitoring/openshift-cluster-monitoring\"
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: MonitoringAssignee: Frederic Branczyk <fbranczy>
Status: CLOSED DUPLICATE QA Contact: Junqi Zhao <juzhao>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: alegrand, anpicker, erooth, 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:
Last Closed: 2019-06-19 08:53:58 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 Stefan Schimanski 2019-06-19 08:44:48 UTC
Description of problem:

CI shows this a lot, like in >50% of the e2e aws runs:

level=fatal msg="failed to initialize the cluster: Could not update operatorgroup \"openshift-monitoring/openshift-cluster-monitoring\" (171 of 338): the server does not recognize this resource, check extension API servers: timed out waiting for the condition"

A number of runs:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/7
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/6
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/11
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/10
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/9

Comment 1 Pawel Krupa 2019-06-19 08:53:58 UTC
Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1721343

*** This bug has been marked as a duplicate of bug 1721343 ***