Bug 1732884

Summary:	Install Fails While Waiting for Cluster Monitoring Operator
Product:	OpenShift Container Platform	Reporter:	Steve Kuznetsov <skuznets>
Component:	Monitoring	Assignee:	Pawel Krupa <pkrupa>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	alegrand, anpicker, erooth, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	buildcop
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:31:08 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 Steve Kuznetsov 2019-07-24 15:29:25 UTC

Initial installation for a cluster to upgrade fails:

level=info msg="Waiting up to 30m0s for the cluster at https://api.ci-op-rn55ww75-77109.origin-ci-int-aws.dev.rhcloud.com:6443 to initialize..."
level=fatal msg="failed to initialize the cluster: Cluster operator monitoring is still updating" 

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/4529#0:build-log.txt%3A30

Comment 1 Pawel Krupa 2019-07-24 16:13:38 UTC

There is a problem with alertmanager stateful set. This might be fixed by updating prometheus-operator to newer version (work in progress in https://github.com/openshift/prometheus-operator/).

Changing version to 4.2.0 as logs suggest this is not related to 4.1.0:

Installing from initial release registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-24-000310

Comment 2 Pawel Krupa 2019-07-26 09:58:35 UTC

This could have been fixed by https://github.com/openshift/prometheus-operator/pull/35

Comment 5 errata-xmlrpc 2019-10-16 06:31:08 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922