Bug 1830121
Summary: | DaemonSet pods tab on console should hide namespace and owner columns (redundant) and instead show node | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> | ||||||
Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 4.5 | CC: | aos-bugs, jokerman, xiaocwan | ||||||
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:34:07 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: | |||||||||
Attachments: |
|
Description
Clayton Coleman
2020-04-30 20:40:16 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1802281 is to fix the namespace issue across all resource lists when a namespace is selected. Move to upcoming sprint as it will be necessary to create separate pod lists or the existing pod list configurable. After discussing with with Sam and Ben, reducing severity to medium as this is not a show stopper. Created attachment 1689744 [details]
Verification screenshot - DS
Created attachment 1689745 [details]
Verification screenshot - Deployment
Checked DaemonSet, ReplicaSet and StatefulSet: updated owner to node Deployments and deployment configs: show owners, but not namespaces Attach screenshot for above two types of resource list column for refer. Verified on 4.5.0-0.nightly-2020-05-19-011623 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 |