Bug 1435007

Summary:	admin users do not get new roles upon upgrade
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Authorization	Assignee:	Ondřej Pražák <oprazak>
Status:	CLOSED ERRATA	QA Contact:	Marek Hulan <mhulan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.8	CC:	adahms, bbuckingham, bkearney, cduryee, inecas, jcallaha, mhulan
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	With this release, the roles included in Red Hat Satellite are now ready only. If any of these roles were previously customized, an editable version of those roles with the name "Cuztomized XXXX" is created when you upgrade your environment to this version.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:42:52 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:	1435022

Description Chris Duryee 2017-03-22 21:45:03 UTC

Description of problem:

If you typically log into your satellite with an admin user that is not the 'admin' user, you may miss out on new roles that are added in new releases. This may cause your superuser to not be so super anymore, causing confusion.

For example, a sysadmin that upgraded from early 6.0 to 6.1 to 6.2 ran into http://projects.theforeman.org/issues/5616. The fix was simple enough, but it would be better if there was some way to alert sysadmins upon upgrade that new roles exist and need to be allocated.

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

Comment 1 Marek Hulan 2017-03-23 12:12:07 UTC

Could you please better define who is considered admin user who is not 'admin' user? I suppose it's a regular user with some role and without admin checkbox checked. If that's the case, we're working on mechanism for doing so in http://projects.theforeman.org/issues/18001, all roles seeded by default will be locked so we can update their permissions on updates. Ideally admin users who are not 'admin' should be using Manager role that should contain all permissions from all plugins once this is finished. However we don't plan to add new permission to roles created by users, we have no clue to which roles they should be added.

Would this address your issue?

Comment 2 Chris Duryee 2017-03-23 12:23:05 UTC

I meant that 'admin' user is the user with login name of 'admin', sorry for not being clear.

I believe 18001 will address this bug. If a user adds themselves as Manager, it sounds like they will get all the permissions needed in the future.

Comment 3 Marek Hulan 2017-03-24 08:29:42 UTC

Ok, thanks. Linking the upstream issue then.

Comment 4 Satellite Program 2017-03-24 10:02:19 UTC

Upstream bug assigned to oprazak

Comment 5 Satellite Program 2017-03-24 10:02:22 UTC

Upstream bug assigned to oprazak

Comment 6 Satellite Program 2017-03-24 16:02:19 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18001 has been resolved.

Comment 12 Bryan Kearney 2018-02-21 16:40:30 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-2018:0336

Comment 13 Bryan Kearney 2018-02-21 16:42:52 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-2018:0336