Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.17.z
Component/s: Storage / Kubernetes
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

    The node pool upgrade being blocked due to one of the pods cannot be removed from the old node.

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

    4.17.21

How reproducible:

    not sure

Steps to Reproduce:

    1. Perform node pool upgrade in HCP cluster
    2. Check the pods on the hosted cluster
    3.

Actual results:

    One of the pods in terminating status and the upgrade cannot proceed.

Expected results:

    Upgrade successfully.

Additional info:

Here is the pod info:
$ oc get po -n <namespace>
NAME                                                    READY   STATUS        RESTARTS       AGE
<REDACTED>-server-0                                          2/2     Running       0              5h15m
<REDACTED>-585fdfdcd4-jnkkn   3/3     Running       1 (5h9m ago)   5h15m
<REDACTED>-f65f7bbc5-p2hhd    0/3     Terminating   56 (9d ago)    31d

Assignee:: Hemant Kumar

Reporter:: Bo Meng

Need Info From:: None

Contributors:: None

QA Contact:: Cameron Meadors

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2025/03/28 3:14 AM

Updated:: 2025/07/14 1:29 PM

Resolved:: 2025/04/11 2:14 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates