Bug 1887431

Summary: [OCP 4.4] KubePodCrashLooping kube-contoller-manager cluster-policy-controller: 6443: connect: connection refused
Product: OpenShift Container Platform Reporter: Johnray Fuller <jrfuller>
Component: kube-controller-managerAssignee: Maciej Szulik <maszulik>
Status: CLOSED DUPLICATE QA Contact: zhou ying <yinzhou>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: aabhishe, aos-bugs, cdaley, dbewley, dougsland, gzaidman, harpatil, hongkliu, jerzhang, knarra, lars, mfojtik, mmohan, mrhodes, mzali, naygupta, nbhatt, ocohen, palonsor, sdodson, tnozicka, vrutkovs, wking
Target Milestone: ---Keywords: Reopened
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1881534 Environment:
[sig-arch] Managed cluster should have no crashlooping pods in core namespaces over four minutes [sig-arch] Managed cluster should have no crashlooping pods in core namespaces over two minutes [Feature:Platform] Managed cluster should have no crashlooping pods in core namespaces over two minutes
Last Closed: 2020-10-23 10:21:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1842002, 1881534    
Bug Blocks:    

Comment 2 Maciej Szulik 2020-10-12 13:12:17 UTC

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

Comment 3 naygupta 2020-10-23 04:46:34 UTC
Hello 

We have a customer hitting this issue and not allowed to upgrade the cluster to 4.5  at this moment.
The customer wants to fix this issue in 4.4.17. 

Do we have any plan to back-port this in 4.4?

If it's possible to backport this to 4.4, it would be very helpful.