This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2196360 - Weird behavior when applying role filters
Summary: Weird behavior when applying role filters
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-08 19:48 UTC by Ricardo Santamaria
Modified: 2024-06-06 16:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:13:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-20617 0 None Migrated None 2024-06-06 16:13:52 UTC

Description Ricardo Santamaria 2023-05-08 19:48:51 UTC 
Description of problem:

For created role has set of filters. 3 have unlimited checked. If create filter that has unlimited UNchecked. 

Version-Release number of selected component (if applicable):

This has been reproduced in latest versions of Satellite 6.13/12/11/10 

How reproducible:
Simply create a role (IE: User Role) and create any filters all unlimited. Then 

Steps to Reproduce:
0. Set any org any location 
1. Create role: example 'User Role'
2. Assign filters all which should be unlimited. For example:
   - Hosts View, Host Delete, Host Create 
   - At this moment all have checked icon for 'Unlimited?' 

3. Now edit one of them, ex: 'Host View' and uncheck the 'unlimited?' option and add filter 'name ~ serverA' and 'Submit' 

At this moment the 'Unlimited?' column has no icon

4. Edit 'Host View' once again. Remove the filter and enable 'Unlimited?' and then submit

Actual results:
There is no checked icon for 'Host View' in the unlimited column.

Expected results:
Once it is any Org/Location and there is no filter the checked icon should be in the 'Unlimited?' column? 

Similar found bugzillas:

Bug 2158725 - In User Role -> Add Filter, Unlimited check selected to all resources, which is not being checked while adding filter 

Bug 1677469 - Filter Fact value with permission view_facts does not take unlimited option in Roles
Comment 2 Adam Ruzicka 2023-10-05 13:03:02 UTC 
When a filter is first created, it gets saved with taxonomy_search empty. On update, this gets filled with a search describing the role's taxonomies, thus making the filter limited.
Comment 3 Eric Helms 2024-06-06 16:13:54 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.