Bug 1914803
Summary: | Some of the "filters" permission changed after the upgrade. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> |
Component: | Content Views | Assignee: | Chris Roberts <chrobert> |
Status: | CLOSED ERRATA | QA Contact: | Devendra Singh <desingh> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 6.9.0 | CC: | ahumbe, chrobert, jsherril, pcreech, sbible |
Target Milestone: | 6.11.0 | Keywords: | Regression, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | https://projects.theforeman.org/issues/33146 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-05 14:28:38 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: |
Description
Devendra Singh
2021-01-11 09:23:43 UTC
Devendra, We've been working on fixing some permission issues we've recently found. The sync plan changes are 100% expected, as previously the ability to 'sync' a sync plan wasn't even governed by a permission, and thus only an admin user could do that. For the Gpg key permissions, these have been replaced with content_credentials. in 6.7 and older, there was a mix of content credentials and gpg key permissions and neither really covered the full apis. However it looks like we might need to 'delete' the old gpg key permissions, i'll leave this bug open to do that. After digging into this more, its actually working as expected. "Content Credentials' are called 'GpgKeys' under the hood. We've renamed just about everything else (Permission names, for example view_content_credentials, controller name, UI), but this internal model name is still around we can work on changing it too, but i think its too risky for 6.9 as its a good bit of refactoring. Based upon comment 2, moving this one to 6.10 as it should have no negative impact on users. Proposing we move to 7.0 due to the risk of backporting this, but going ahead and doing the work now so that it will be ready for 7.0 (and doesn't get kicked down the road again). Upstream bug assigned to chrobert Upstream bug assigned to chrobert Verified on 6.11 Snap15. Before Upgrade the filter's permission Permissions: "view_sync_plans, create_sync_plans, edit_sync_plans, destroy_sync_plans, sync_sync_plans" After Upgrade the filter's permission Permissions: "view_sync_plans, create_sync_plans, edit_sync_plans, destroy_sync_plans, sync_sync_plans" 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 (Moderate: Satellite 6.11 Release), 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-2022:5498 |