Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1435007 - admin users do not get new roles upon upgrade
Summary: admin users do not get new roles upon upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Authorization
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Marek Hulan
URL:
Whiteboard:
Depends On:
Blocks: 1435022
TreeView+ depends on / blocked
 
Reported: 2017-03-22 21:45 UTC by Chris Duryee
Modified: 2019-09-26 15:39 UTC (History)
7 users (show)

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.
Clone Of:
Environment:
Last Closed: 2018-02-21 16:42:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18001 0 None None None 2017-03-24 08:29:42 UTC

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
Note You need to log in before you can comment on or make changes to this bug.