Bug 2088727 - oc is not reporting pods with status NodeLost for Daemonset pods when a node is marked NotReady
Summary: oc is not reporting pods with status NodeLost for Daemonset pods when a node ...
Keywords:
Status: CLOSED DUPLICATE of bug 2088726
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-20 10:33 UTC by Christian Passarelli
Modified: 2022-05-25 10:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-25 10:43:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Christian Passarelli 2022-05-20 10:33:04 UTC 
Description of problem:
oc reports the daemonset pods status as "Running" if the related node is "NotReady".

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

How reproducible:
100% 

Steps to Reproduce:
1. Manually shutdown a cluster node
2. Wait until the node became NotReady
3. Run "oc get pod" in any of the namespaces having Daemonsets pods to see status is not changed from "Running" for the ones running on the shutter down node. For example, execute "oc get pod -n openshift-dns -o wide" 

Actual results:
oc still report the pod as "Running".

Expected results:
The pod shouldn't be marked Running if the node is NotReady


Additional info:
In Openshift 3.11 oc reports daemonset pods as "NodeLost" when the node is "NotReady"
Comment 2 Maciej Szulik 2022-05-25 10:43:19 UTC 

*** This bug has been marked as a duplicate of bug 2088726 ***
Note You need to log in before you can comment on or make changes to this bug.