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.
Description of problem:
Setting a filter to Unlimited completes successfully in the UI but afterwards the setting is not marked in the filters table and when revisiting the filter details the Unlimited checkbox is unchecked.
Version-Release number of selected component (if applicable):
Sat 6.5 snap 8
How reproducible:
always
Steps to Reproduce:
1. create a custom role
2. add filter, set resource type and permission. If Unlimited is checked by default, uncheck it manually, then check it again.
3. Submit
Actual results:
The role's filters table shows Unlimited as unchecked, when editing the filter the checkbox is unchecked.
Additional info:
Does not apply to the Override checkbox
Checked again on 6.5 snap 13. It is reproducible only if role is assigned to one or more organizations, location setting does not have an effect. Looking at 6.4 Satellite I can reproduce the same problem.
This is expected behavior, per the inline help:
"If the unlimited field is enabled, the filter applies to all resources of the selected type. If the unlimited field is disabled, you can specify further filtering using Foreman search syntax in the search field.> If the role is associated with organizations or locations, the filters are not considered unlimited as they are scoped accordingly."
The most important here to notice here, if filter are associated with some org/log, they are limited. The experience has changed over last few versions a bit, since we encourage people to assign org/locs to the role. So there may be another RFE that will rename that checkbox or change the logic in showing the checkmark, but I'm closing this as NOTABUG. Please reopen if I missed something.