Bug 1940916 - Pods stuck in terminating when a cluster upgrade is triggered or during a deployment rollout
Summary: Pods stuck in terminating when a cluster upgrade is triggered or during a de...
Keywords:
Status: CLOSED DUPLICATE of bug 1952224
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 4.8.0
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
: 1929685 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-19 14:30 UTC by Anandhu B Raj
Modified: 2021-04-30 15:38 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-30 15:38:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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. ***


Note You need to log in before you can comment on or make changes to this bug.