Bug 1655428

Summary: Not able to see logs for block-manager user
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Uday kurundwade <ukurundw>
Component: Ceph-DashboardAssignee: Ernesto Puerta <epuertat>
Status: CLOSED ERRATA QA Contact: Uday kurundwade <ukurundw>
Severity: high Docs Contact: Anjana Suparna Sriram <asriram>
Priority: unspecified    
Version: 3.2CC: ceph-eng-bugs, ceph-qe-bugs, mkasturi, tchandra, tserlin
Target Milestone: rc   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:45:18 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 Flags
Screenshot of log page none

Description Uday kurundwade 2018-12-03 07:16:23 UTC
Created attachment 1510813 [details]
Screenshot of log page

Description of problem:
Not able to see logs for block-manager user

Version-Release number of selected component (if applicable):
ceph-common-12.2.8-43.1.el7cp.x86_64
ceph-mgr-12.2.8-43.1.el7cp.x86_64
ceph-ansible-3.2.0-0.1.rc4.el7cp.noarch

How reproducible:
Always

Steps to Reproduce:
1.Install ceph storage
2.Install "dashboard v2" by running ansible playbook
3.Login to dashboard after installation of dashboard v2
4.Create new user and assign "Block manager" role to that user. 
5.Log in with newly created Block manager user.
6.Navigate Cluster status->Logs

Actual results:
Log shows blank info

Expected results:
Log should display

Additional info:
Not able to see logs for cephfs-manager user also

Comment 5 Ernesto Puerta 2019-11-20 19:08:50 UTC
This has been fixed since 3.2. Now block-manager role does not have access to Ceph logs, only Block/RBD related configuration.

Comment 9 errata-xmlrpc 2020-01-31 12:45:18 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:0312