Bug 1821625
| Summary: | normal user get 403 Forbidden error when viewing Network In and Network Out metric on Pod Details page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> | ||||
| Component: | Management Console | Assignee: | Yadan Pei <yapei> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.4 | CC: | aos-bugs, bpeterse, jokerman, rhamilto, spadgett, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.4.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: Namespace is required for normal users to view Network In and Network Out metrics on the Pod Details page.
Consequence: Normal users cannot view Network In and Network Out metrics on the Pod Details page since the code does not supply a namespace.
Fix: Add a namespace prop to Network In and Network Out metrics on the Pod Details page.
Result: Normal users can view Network In and Network Out metrics on the Pod Details page.
|
Story Points: | --- | ||||
| Clone Of: | 1819628 | Environment: | |||||
| Last Closed: | 2020-05-26 16:50:32 UTC | Type: | --- | ||||
| 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: | 1819628 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Yadan Pei
2020-04-07 09:09:18 UTC
PR opened, awaiting cherry pick approval. Created attachment 1689731 [details]
Normal User Can View Pod Metrics
Now normal user can view pod Network In and Network Out metrics successfully
Verified on 4.4.0-0.nightly-2020-05-18-014003
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:2180 |