Bug 2103215

Summary:	[4.8] Pod stuck in Terminating, runc init process frozen
Product:	OpenShift Container Platform	Reporter:	Peter Hunt <pehunt>
Component:	Node	Assignee:	Peter Hunt <pehunt>
Node sub component:	CRI-O	QA Contact:	Sunil Choudhary <schoudha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	abraj, aos-bugs, atomlin, djuran, fromani, jdesousa, jgato, jkaur, kir, kiyyappa, llopezmo, minmli, mrobson, nagrawal, nkashyap, obockows, pehunt, peter.hunter, rkshirsa, ssonigra, tsweeney
Version:	4.6
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	runc-1.0.0-99.rhaos4.8.git93d7d28.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1903228
Clones:	2103217 (view as bug list)		Environment:
Last Closed:	2022-08-09 12:52:44 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:	1903228
Bug Blocks:	2103217

Comment 3 Sunil Choudhary 2022-07-14 11:10:38 UTC

% oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2022-07-14-012938   True        False         111m    Cluster version is 4.8.0-0.nightly-2022-07-14-012938

sh-4.4# rpm -q runc
runc-1.0.0-99.rhaos4.8.git93d7d28.el8.x86_64

Checked by deleting multiple pods before they get ready, don't see error messages in kubelet logs.

Comment 6 errata-xmlrpc 2022-08-09 12:52:44 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.8.47 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/RHBA-2022:5889

Comment 7 Jose Gato 2022-08-11 07:30:06 UTC

Sorry, I am confused, was this bug not already fixed previously?