+++ 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:
Jira issue: https://issues.redhat.com/browse/ODC-2679
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.
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