Bug 1786272

Summary: Pods number for Daemon Set is 0 on project "Workloads" page
Product: OpenShift Container Platform Reporter: Yanping Zhang <yanpzhan>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.0CC: aballant, aos-bugs, bpeterse, jokerman, nmukherj, sbudhwar, spadgett, yapei
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1786271 Environment:
Last Closed: 2020-03-10 23:52:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1786271    
Bug Blocks:    

Description Yanping Zhang 2019-12-24 07:22:10 UTC
+++ This bug was initially created as a clone of Bug #1786271 +++

Description of problem:
Create daemon set in project, and all pods for daemon set are running, check daemon set under project "Workloads" tab, it shows 0/0 pods for daemon set.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-22-174103

How reproducible:
Always

Steps to Reproduce:
1.Create Daemon set in project.
2.After pods are running, check Daemon Set under "Workloads" tab on project page.
3.

Actual results:
2.It shows 0/0 pods for daemonset.

Expected results:
3. Should show 3/3 pods.(There are 3 workers, and 3 pods are running here.)

Additional info:

Comment 1 Andrew Ballantyne 2020-01-20 19:36:13 UTC
Jira issue: https://issues.redhat.com/browse/ODC-2679

Comment 4 Yanping Zhang 2020-03-02 06:57:39 UTC
Checked on OCP 4.3 env with payload 4.3.0-0.nightly-2020-03-01-224924, now the pods number for daemonset is correct under project "Workloads" tab.
The bug is fixed, so move it to Verified.

Comment 6 errata-xmlrpc 2020-03-10 23:52:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0676