Bug 1884676

Summary:	kube-controller-manager degraded after upgrade (4.4.16 to 4.5.11)
Product:	OpenShift Container Platform	Reporter:	Naveen Malik <nmalik>
Component:	kube-controller-manager	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED DUPLICATE	QA Contact:	zhou ying <yinzhou>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, mfojtik, travi
Target Milestone:	---	Keywords:	ServiceDeliveryImpact
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:	2020-10-05 13:16:42 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 Naveen Malik 2020-10-02 16:02:05 UTC

Description of problem:
kube-controller-manager becomes degraded after upgrade and doesn't always recover.  This is observed on OSD e2e tests.

Version-Release number of selected component (if applicable):
4.5.11

How reproducible:
Intermittent

Steps to Reproduce:
1. create OSD clsuter version 4.4.16
2. upgrade to 4.5.11
3.

Actual results:
kube-controller-manager is degraded

Expected results:
kube-controller-manager is not degraded

Additional info:
will attach must-gather in a bit..

Comment 2 Naveen Malik 2020-10-02 17:29:50 UTC

After the following the kube-controller-manager is no longer degraded:

oc patch kubecontrollermanager/cluster --type merge -p "{\"spec\":{\"forceRedeploymentReason\":\"Forcing new revision with random number $RANDOM to make message unique\"}}"

from https://access.redhat.com/solutions/4849711

Comment 3 Maciej Szulik 2020-10-05 13:16:42 UTC

This is being fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1874597

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