Bug 1940916

Summary: Pods stuck in terminating when a cluster upgrade is triggered or during a deployment rollout
Product: OpenShift Container Platform Reporter: Anandhu B Raj <abraj>
Component: NodeAssignee: Ryan Phillips <rphillips>
Node sub component: Kubelet QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: high CC: aos-bugs, fpaoline, fsilva, harpatil, llopezmo, luaparicio, mdeloren, nagrawal, openshift-bugs-escalate, rphillips, saniyer, tsweeney
Version: 4.6   
Target Milestone: ---   
Target Release: 4.8.0   
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-30 15:38:12 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 Anandhu B Raj 2021-03-19 14:30:22 UTC 
Description of problem:

One customer is seeing that some pods are hanging in a terminating state when he triggered a cluster upgrade or when he do a deployment rollout. The only way to get rid of this is to force terminate the pods. This can be observed for any pods irrespective of project and nodes.

Found a similar bug with 4.7 :

https://bugzilla.redhat.com/show_bug.cgi?id=1915085

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

Current OCP version:

version   4.6.17    



Additional info:

CU faced this issue with 4.5 initially then they upgraded to 4.6, but still they are facing this issue.

I will attach the logs.
Comment 22 Harshal Patil 2021-04-29 09:31:49 UTC 
*** Bug 1929685 has been marked as a duplicate of this bug. ***