Bug 1851404 - kcm pod crashloops because port is already in use
Summary: kcm pod crashloops because port is already in use
Keywords:
Status: CLOSED DUPLICATE of bug 1851397
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.4.z
Assignee: Tomáš Nožička
QA Contact: zhou ying
URL:
Whiteboard:
Depends On: 1851390
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-26 12:56 UTC by Tomáš Nožička
Modified: 2020-06-26 12:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1851390
Environment:
Last Closed: 2020-06-26 12:58:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomáš Nožička 2020-06-26 12:56:28 UTC 
+++ This bug was initially created as a clone of Bug #1851390 +++

+++ This bug was initially created as a clone of Bug #1851389 +++

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 1 Tomáš Nožička 2020-06-26 12:58:15 UTC 

*** This bug has been marked as a duplicate of bug 1851397 ***
Note You need to log in before you can comment on or make changes to this bug.