Created attachment 1647459 [details] daemonset 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:
Hi Sam, Could you let us know why it's changed to Dev Console? When user view project workloads at Administration perspective Home -> Projects -> Workloads, the number always show 0 of 0 pods Also can we fix it in 4.3.0? or even 4.3.z?
Added to JIRA backlog: https://issues.redhat.com/browse/ODC-2771
(In reply to Yadan Pei from comment #1) > > Could you let us know why it's changed to Dev Console? When user view > project workloads at Administration perspective Home -> Projects -> > Workloads, the number always show 0 of 0 pods This view shares code with the topology view in the dev console, and they currently own that code. (Christian, let me know if you disagree with that statement :) A lot of pages show up in both perspectives. I agree we need to backport to 4.3.z.
Sam, really appreciate your explanation.
Verified on CI build: 4.4.0-0.ci-2020-02-15-184748 Chrome browser: 76.0.3809.132
Created attachment 1663579 [details] Pods number for Daemon Set is not 0 on project "Workloads" page
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:0581