Bug 1721528

Summary:	route api should be responsive throughout upgrade
Product:	OpenShift Container Platform	Reporter:	Justin Pierce <jupierce>
Component:	openshift-apiserver	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED DUPLICATE	QA Contact:	Xingxing Xia <xxia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jokerman, mfojtik, mmccomas
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-07-24 10:15:06 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 Justin Pierce 2019-06-18 13:36:55 UTC

Description of problem:
During an upgrade from 4.1.1 to 4.1.2, it was observed that the route API failed to respond to requests from the monitoring cluster operator. This cause the monitoring cluster operator to raise Degraded.

14:51:26  ClusterOperator not fully ready: monitoring
14:51:26      Available=False  :: 
14:51:26      Progressing=True  :: Rolling out the stack.
14:51:26      Degraded=True  :: Failed to rollout the stack. Error: running task Updating configuration sharing failed: failed to retrieve Alertmanager host: getting Route object failed: the server is currently unable to handle the request (get routes.route.openshift.io alertmanager-main)

The condition ultimately recovered by itself, but, per Clayton, "that should never happen."

Version-Release number of selected component (if applicable):
4.1.1/4.1.2

Steps to Reproduce:
1. Constantly monitor the Conditions of each clusteroperator during an upgrade.
2.
3.

Comment 1 Michal Fojtik 2019-07-24 10:15:06 UTC


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