Bug 1946418

Summary:	[4.7] Pod stuck in Terminating state
Product:	OpenShift Container Platform	Reporter:	Ravi Trivedi <travi>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Node sub component:	Kubelet	QA Contact:	Sunil Choudhary <schoudha>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs, maschmid, rphillips
Version:	4.7	Keywords:	ServiceDeliveryImpact
Target Milestone:	---
Target Release:	---
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:	2021-04-07 13:34:55 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:

Description Ravi Trivedi 2021-04-06 04:25:28 UTC

Description of problem:

Recently, came across couple of instances where pods are stuck in terminating state on master nodes.

Relevant error:
~~~
CreatePodSandbox for pod "fluentd-hrzqd_openshift-logging(e2f46d75-ec07-419a-84f0-95a4aee91777)" failed: rpc error: code = Unknown desc = error reading container (probably exited) json message: EOF
~~~

Version-Release number of selected component (if applicable):
- 4.7.2
- 4.7.4 

Additional info:
- Issue seen on AWS platform (OSD cluster)

The issue seems to be very similar to BZ https://bugzilla.redhat.com/show_bug.cgi?id=1915085 which was fixed in 4.7.0.

Comment 4 Red Hat Bugzilla 2023-09-15 01:04:39 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days