Project

General

Profile

Bug #21342

Role needs to be updated if their permissions changed in new version

Added by Marek Hulán about 3 years ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1501414

Description of problem:
After upgrading from 6.2 to 6.3, The number of filters in 'Oranization Admin' differs than freshly installed satellite 6.3

Fresh Satellite 6.3 has 61 filters in Organization Admin role, and
Upgraded Satellite 6.3 has 59 filters in Organization Admin role

The two missing filters in upgraded sat 6.3 are 'Key Pair' and 'Ssh key'

Version-Release number of selected component (if applicable):
Satellite 6.3 snap 19

How reproducible:
Always

Steps to Reproduce:
1. Upgrade Satellite 6.2 to 6.3
2. Have one fresh satellite 6.3
3. Compare filters of 'organization admin' role between upgraded satellite 6.3 and fresh satellite 6.3

Actual results:
Two filters are missing in organization admin role, those are:
'Key pair' and 'Ssh Key'

Expected results:
All Roles and their filters in Upgraded satellite 6.3 and fresh sat 6.3 should be same.

  • Additional notes:*

The same happens for every change in default roles in Foreman core, no need to run any upgrade process. It should work the same way it works for plugins


Related issues

Related to Foreman - Bug #20812: Extend core roles based on what's in RolesListDuplicate2017-08-31
Related to Foreman - Bug #21496: Roles not properly removing permissionsClosed2017-10-27
Related to Foreman - Bug #24697: foreman-rake db:seed fails on upgrade to Foraman 1.17.1Closed
Blocks Foreman - Bug #21343: Organization admin should he able to work with full multitenancyClosed2017-10-16

Associated revisions

Revision 5878c99f (diff)
Added by Marek Hulán about 3 years ago

Fixes #21342 - fix core roles seeding

Core roles should always be up to date based on what's defined in seed
files. Users have no other way to update locked roles in newer Foreman
versions.

History

#1 Updated by Marek Hulán about 3 years ago

  • Target version set to 1.16.0-RC2
  • Assignee set to Marek Hulán
  • Category set to 218
  • Subject changed from Role needs to be updated if their permissions changed in new version to Role needs to be updated if their permissions changed in new version

#2 Updated by The Foreman Bot about 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4916 added

#3 Updated by Marek Hulán about 3 years ago

  • Blocks Bug #21343: Organization admin should he able to work with full multitenancy added

#4 Updated by Marek Hulán about 3 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#5 Updated by Marek Hulán about 3 years ago

  • Legacy Backlogs Release (now unused) set to 296

#6 Updated by Marek Hulán almost 3 years ago

  • Related to Bug #20812: Extend core roles based on what's in RolesList added

#7 Updated by Marek Hulán almost 3 years ago

  • Related to Bug #21496: Roles not properly removing permissions added

#8 Updated by Tomer Brisker about 2 years ago

  • Related to Bug #24697: foreman-rake db:seed fails on upgrade to Foraman 1.17.1 added

#9 Updated by Tomer Brisker 3 months ago

  • Category changed from 218 to Users, Roles and Permissions

Also available in: Atom PDF