Bug 1826002

Summary:	Refresh ceph dashboard user role
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Francesco Pantano <fpantano>
Component:	Ceph-Ansible	Assignee:	Francesco Pantano <fpantano>
Status:	CLOSED ERRATA	QA Contact:	Sunil Angadi <sangadi>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0	CC:	aschoen, ceph-eng-bugs, fpantano, gfidente, gmeno, hyelloji, jbrier, nthomas, sangadi, tserlin, ykaul
Target Milestone:	z1	Keywords:	Triaged
Target Release:	4.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-ansible-4.0.24-1.el8cp, ceph-ansible-4.0.24-1.el7cp	Doc Type:	Bug Fix
Doc Text:	.Ceph Ansible updates the privileges of the dashboard admin user after initial install Previously, `ceph-ansible` could only set the privileges of the dashboard user when it was first created. Running the playbooks after changing `dashboard_admin_user_ro: false` from its original setting during install would not update the privileges of the user. In {storage-product} 4.1z1 `ceph-ansible` has been updated to support changing the dashboard user privileges on successive runs of the playbooks.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-20 14:21:03 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:
Bug Depends On:
Bug Blocks:	1760354, 1816167

Description Francesco Pantano 2020-04-20 16:40:37 UTC

Description of problem:

ceph-ansible supports the dashboard ceph mode feature and the user can be created with read-only permissions.
In the current state the role is set only when the user is created, and there's no way to change it if the user exists.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 12 errata-xmlrpc 2020-07-20 14:21:03 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/RHSA-2020:3003