Bug 1807275 - Daemon sets shows incorrect pod text
Summary: Daemon sets shows incorrect pod text
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Aritra Roy
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks: 1810972
TreeView+ depends on / blocked
 
Reported: 2020-02-26 01:02 UTC by Aritra Roy
Modified: 2020-07-13 17:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:21:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
pod ring text for daemon sets (8.78 KB, image/png)
2020-02-26 01:02 UTC, Aritra Roy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4398 0 None closed Bug 1807275: fix pod text for daemon workload 2020-06-23 08:50:31 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:22:05 UTC

Internal Links: 1810972

Description Aritra Roy 2020-02-26 01:02:21 UTC
Created attachment 1665781 [details]
pod ring text for daemon sets

Description of problem:

Pod ring text shows "Scaled to 0" for a daemon set although there are pods running

Version-Release number of selected component (if applicable):
4.5.0-0.ci-2020-02-25-152421

How reproducible:
always

Steps to Reproduce:
1.create a daemon set from workloads menu in admin perspective
2.the workload for the daemon set shows the above behaviour in topology

Actual results:
the pod ring text shows "Scaled to 0" although there are pods running

Expected results:
the pod ring text should show "3 pods"

Additional info:

Comment 3 Gajanan More 2020-03-06 08:34:50 UTC
I have validated this bug on:
Build: 4.5.0-0.ci-2020-03-05-232742
Browser: Google Chrome Version 78.0.3904.108
Marking this as verified.

Comment 5 errata-xmlrpc 2020-07-13 17:21:31 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:2409


Note You need to log in before you can comment on or make changes to this bug.