Bug 1902204

Summary:	kuryr-cni cannot start new thread
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Networking	Assignee:	Michał Dulko <mdulko>
Networking sub component:	kuryr	QA Contact:	GenadiC <gcheresh>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	high	CC:	itbrown, mdulko
Version:	4.7
Target Milestone:	---
Target Release:	4.6.z
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-12-14 13:51:28 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:	1891559
Bug Blocks:

Comment 3 Itzik Brown 2020-12-06 14:06:23 UTC

$ oc get pods -n openshift-kuryr
NAME                               READY   STATUS    RESTARTS   AGE
kuryr-cni-4lf8k                    1/1     Running   0          44h
kuryr-cni-86jcg                    1/1     Running   0          45h
kuryr-cni-c55tw                    1/1     Running   0          44h
kuryr-cni-fdgj9                    1/1     Running   0          45h
kuryr-cni-nlbvv                    1/1     Running   0          45h
kuryr-cni-v8k9q                    1/1     Running   0          44h
kuryr-controller-97c97c7cb-l2lzq   1/1     Running   1          45h

4.6.0-0.nightly-2020-12-04-073553
OSP13 2020-11-13.1

Comment 6 errata-xmlrpc 2020-12-14 13:51:28 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 (Moderate: OpenShift Container Platform 4.6.8 security and bug fix update), 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/RHSA-2020:5259