Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2088727

Summary:	oc is not reporting pods with status NodeLost for Daemonset pods when a node is marked NotReady
Product:	OpenShift Container Platform	Reporter:	Christian Passarelli <cpassare>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
oc sub component:	oc	QA Contact:	zhou ying <yinzhou>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	mfojtik
Version:	4.10
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:	2022-05-25 10:43:19 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 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 ***