Bug 1851389

Summary:	kcm pod crashloops because port is already in use
Product:	OpenShift Container Platform	Reporter:	Tomáš Nožička <tnozicka>
Component:	kube-controller-manager	Assignee:	Tomáš Nožička <tnozicka>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.6	CC:	aos-bugs, gzaidman, mfojtik
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1851390 (view as bug list)		Environment:
Last Closed:	2020-10-27 16:09:46 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:
Bug Depends On:
Bug Blocks:	1851390

Description Tomáš Nožička 2020-06-26 12:10:34 UTC

kcm pod crashloops because port is already in use. I saw a case with cluster-policy-manager container but it's not limited to it.

Crashlooping triggers alerts and adds backoff for the pod so it start slower.

Container can be restarted while the pods stays. For that reason, we need to check the port availability in the same process as we listen, not in an init container which isn't re-run.

Comment 4 Maciej Szulik 2020-07-06 11:09:44 UTC

*** Bug 1853889 has been marked as a duplicate of this bug. ***

Comment 5 Maciej Szulik 2020-07-06 15:32:37 UTC

*** Bug 1853889 has been marked as a duplicate of this bug. ***

Comment 6 Gal Zaidman 2020-07-06 15:34:57 UTC

*** Bug 1853889 has been marked as a duplicate of this bug. ***

Comment 7 Gal Zaidman 2020-07-06 15:58:46 UTC

This is breaking oVirt, as stated on https://bugzilla.redhat.com/show_bug.cgi?id=1853889

Comment 9 errata-xmlrpc 2020-10-27 16:09:46 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196