Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1767497

Summary: Compute Resource filter does not correctly allow Refresh Cache
Product: Red Hat Satellite Reporter: Yifat Makias <ymakias>
Component: Users & RolesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: bkearney, egolov, mhulan, tbrisker
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-2.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yifat Makias 2019-10-31 15:04:46 UTC 
I am trying to set up new filters and found one I believe doesnt work.   It appears according to:
https://github.com/theforeman/foreman/blob/c236a809e044804f801440174f27b9a5c5c561ca/app/registries/foreman/access_permissions.rb#L76
that the refresh cache is part of the view_compute_resources permission.  When I divide the Compute Resources into two sections; one for unlimited access and one to control a specific compute resource, the option to Refresh Cache on the compute resources goes away for everyone except admins.  

Am I setting this correctly, everything else works as expected:
https://i.imgur.com/3enDPqM.png

How do I get refresh cache to show for non admins, but still prevent everything else in my NON unlimited filter?
Comment 1 Yifat Makias 2019-10-31 15:04:49 UTC 
Created from redmine issue https://projects.theforeman.org/issues/25936
Comment 2 Yifat Makias 2019-10-31 15:04:52 UTC 
Upstream bug assigned to None
Comment 4 Marek Hulan 2019-11-01 11:00:58 UTC 
*** Bug 1767493 has been marked as a duplicate of this bug. ***
Comment 5 Bryan Kearney 2019-11-05 20:41:47 UTC 
Upstream bug assigned to ymakias
Comment 6 Bryan Kearney 2019-11-05 20:41:49 UTC 
Upstream bug assigned to ymakias
Comment 7 Bryan Kearney 2019-11-06 17:01:00 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25936 has been resolved.
Comment 8 Peter Ondrejka 2020-06-05 08:50:57 UTC 
Verified on Satellite 6.8 snap 2, the refresh cache is displayed for users with view_compute_resources permission
Comment 11 errata-xmlrpc 2020-10-27 12:59:24 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 (Important: Satellite 6.8 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-2020:4366