Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1804884

Summary: Unable to view links to the dashboards in the web console menu
Product: OpenShift Container Platform Reporter: bpeterse
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.zCC: alegrand, anpicker, aos-bugs, bpeterse, cvogel, erooth, jhadvig, jokerman, kakkoyun, kechung, lcosic, mloibl, pkrupa, rhowe, spadgett, spasquie, surbania, yapei
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1777486 Environment:
Last Closed: 2020-05-13 21:59:24 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: 1777486    
Bug Blocks:    

Comment 5 Yadan Pei 2020-03-09 02:43:47 UTC 
Now Monitoring -> Dashboards menu is the place user can view the dashboard, verified on 4.4.0-0.nightly-2020-03-08-213224
Comment 6 Yadan Pei 2020-03-09 06:37:02 UTC 
1. grant normal user metrics reader role
# cat metrics-reader-cluster-role.yaml 
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: metrics-reader
rules:
  - apiGroups:
      - ''
    resources:
      - namespaces
    verbs:
      - get
      - list
      - watch
# oc create -f metrics-reader-cluster-role.yaml 
clusterrole.rbac.authorization.k8s.io/metrics-reader created
# oc adm policy add-cluster-role-to-user metrics-reader yapei1 
clusterrole.rbac.authorization.k8s.io/metrics-reader added: "yapei1"

2. Normal user 'yapei1' login to the cluster and visit Monitoring, user can see Dashboards menu, also user can view dashboards successfully
Comment 8 errata-xmlrpc 2020-05-13 21:59:24 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:0581