Bug 1775156 - Explore type access review tab incorrectly says "at the cluster scope"
Summary: Explore type access review tab incorrectly says "at the cluster scope"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.3.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1775217
TreeView+ depends on / blocked
 
Reported: 2019-11-21 13:53 UTC by Samuel Padgett
Modified: 2020-01-23 11:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In the web console "Access Review" tab under Home -> Explore, the message incorrectly stated "at the cluster scope" when checking access for a resource in a specific project. The message has been corrected.
Clone Of:
: 1775217 (view as bug list)
Environment:
Version: 4.3.0-0.ci-2019-11-20-121416 Cluster ID: a4b30cf7-41e8-47f3-ba84-b953c06bca5e Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:70.0) Gecko/20100101 Firefox/70.0
Last Closed: 2020-01-23 11:13:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3520 0 'None' 'open' 'Bug 1775156: Fix access review message for namespaced resources' 2019-11-21 13:55:42 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:14:04 UTC

Description Samuel Padgett 2019-11-21 13:53:15 UTC
When checking access in a particular project, the access review tab will always show "at the cluster scope" in the message even if a namespace is selected.

Comment 2 XiaochuanWang 2019-11-25 02:00:09 UTC
Now the message is correct and clear such as "The following subjects can create configmaps in namespace default."
Verified on 4.3.0-0.nightly-2019-11-24-183610

Comment 4 errata-xmlrpc 2020-01-23 11:13:47 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:0062


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