Bug 1871122

Summary:	Crio panic suddenly
Product:	OpenShift Container Platform	Reporter:	yaoli
Component:	Node	Assignee:	Urvashi Mohnani <umohnani>
Status:	CLOSED ERRATA	QA Contact:	Sunil Choudhary <schoudha>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.3.z	CC:	aos-bugs, dornelas, dwalsh, jokerman, nagrawal, sjenning, tsweeney
Target Milestone:	---
Target Release:	4.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:30:14 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:	1186913

Comment 15 Sunil Choudhary 2020-09-09 17:06:11 UTC

Verified on 4.6.0-0.nightly-2020-09-09-003430. Created multiple pods in multiple projects and then deleted them. I do not see crio panic or connection refused message in logs.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2020-09-09-003430   True        False         10h     Cluster version is 4.6.0-0.nightly-2020-09-09-003430

Comment 17 errata-xmlrpc 2020-10-27 16:30:14 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