Bug 1807275
| Summary: | Daemon sets shows incorrect pod text | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Aritra Roy <ariroy> | ||||
| Component: | Dev Console | Assignee: | Aritra Roy <ariroy> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4 | CC: | aos-bugs, gamore, nmukherj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-13 17:21:31 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1810972 | ||||||
| Attachments: |
|
||||||
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. 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 |
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: