2148439 – Better content view filtering representation for packages vs modular packages

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 2148439 - Better content view filtering representation for packages vs modular packages

Summary: Better content view filtering representation for packages vs modular packages

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Content Views
Sub Component:
Version:	6.12.0
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	low
Target Milestone:	6.15.0
Assignee:	Samir Jha
QA Contact:	Cole Higgins
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-11-25 13:45 UTC by Taft Sanders
Modified:	2024-04-23 17:12 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2024-04-23 17:12:50 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	36683	Normal	Ready For Testing	Better content view filtering representation for packages vs modular packages	2023-09-05 14:38:40 UTC
Red Hat Issue Tracker	SAT-18727	None	None	None	2023-06-30 12:03:46 UTC
Red Hat Product Errata	RHSA-2024:2010	None	None	None	2024-04-23 17:12:52 UTC

Description Taft Sanders 2022-11-25 13:45:54 UTC

Description of problem:
When creating a content view filter for a package by name, I can see mixed results with the filter working as expected due to packages being modular and not being considered for RPM content view filters.

A better representation of what packages would be affected by a filter or certain type should be created.

Version-Release number of selected component (if applicable):
satellite-6.12.0-4.el8sat.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Create a content view with rhel-7-server-rpms repo only and add the filter to exclude RPM "389-ds-base". At the time of this writing, this filters out 55 packages which would be correct.

2. Create another content view with the "Red Hat Satellite Maintenance 6.12 for RHEL 8 x86_64 RPMs" with a filter to exclude package "rubygem-clamp" (all archs, all versions). This filters out nothing. Create another filter for this same content view and filter out "*" for the package name (all archs, all versions) and it filters out only "satellite-clone".
3.This is because all packages in the Satellite Maintenance 6.12 for RHEL 8 (at this time) are modular except for 1 (satellite-clone). This is not explained or understandable from the content view filter screen without having to navigate to other pages on the Satellite.

Actual results:
See "Steps to reproduce"

Expected results:
{BEST OPTION}
Inclusion/Exclusion should be applied to the repository no matter what the status of modularity or repository contains the stream its associated with.
{NEXT BEST OPTION}
WebUI should display the package's modularity status along with the stream they are associated with everywhere it's viewable to see packages:
- https://satelite.example.com/content_views/:content_view_id/versions/:version_id/rpmPackages
- https://satelite.example.com/packages
- https://satelite.example.com/products/:product_id/repositories/:repository_id
- etc

Additional info:
With the introduction of streams and modularity in RHEL 8 there has been a lot of confusion on why won't systems just update to the latest like yum always has. If DNF is going to treat RPMs differently at the OS level I believe Satellite should also reclass them as a "modular package" as opposed to including them under the umbrella term of "packages".

Comment 1 Taft Sanders 2022-11-25 17:02:54 UTC

Looks like it's user error on my part. The packages are modular so they are not filtered out by the RPM filter:

# curl https://bombsat612.d.sysmgmt.cee.redhat.com/katello/api/packages/?repository_id=4 | json_reformat | grep -e \"name -e modular
            "name": "rubygem-clamp",
            "modular": true,
            "name": "rubygem-foreman_maintain",
            "modular": true,
            "name": "rubygem-highline",
            "modular": true,
            "name": "satellite-clone",
            "modular": false,
            "name": "satellite-maintain",
            "modular": true,

With this point brought up though, this repository is a dependency repository for the Satellite-Capsule 6 and Satellite 6 repositories. The streams don't actually live in the "Red Hat Satellite Maintenance 6.12 for RHEL 8 x86_64 RPMs", so there is no stream to filter out as well. I understand this is probably a very specific use case and probably not reproducible from any other repository offered by Red Hat, but as a user without intimate knowledge of modules I would have the following question:

- As a user, how would I know my filter is working correctly for a repository (Red Hat or 3rd party) to remove packages if one does not fully understand modules, streams, cross repository dependency for a repository listed as having packages and no module streams and having packages that are modular?

(In the Satellite WebUI it shows the "Red Hat Satellite Maintenance 6.12 for RHEL 8 x86_64 RPMs" as having 5 packages (as of today) and 0 module streams.)

- Outside of the API example above and the package search page on the WebUI, how could a user know (preferably from the CV filter screen) that these packages are unaffected by the filter because they are listed as modules and also not affected by module stream filters because they are dependencies of another repository's stream?


**Changing this to an RFE to provide better visual understanding for module packages unaffected by content view filters**

Comment 3 Maria Svirikova 2023-08-15 10:34:57 UTC

Based on the discussion last week we need to add some helper text.
1. When opening a Matching content modal, add a sentence to the empty state: 
"Package filters don’t apply to modular packages."

2. Add a question mark icon to the matching content modal(see https://www.patternfly.org/components/modal/design-guidelines#modals-with-help) with a helper text:
"Matching RPMs based on your created filter rule. Remember, package filters don't apply to modular packages." 

3. Add a question mark icon to the Create filter with a helper text:
"Use filters to include or restrict certain content. When selecting RPMs, be aware that, package filters don't apply to modular packages." 

Pinging doc team to check the microcopy @bangelic

Comment 4 Brian Angelica 2023-08-15 13:23:45 UTC

3. Add a question mark icon to the Create filter with a helper text:
"Use filters to include or restrict certain content. When selecting RPMs, be aware that, package filters don't apply to modular packages." 

Remove extra comma so that it reads:
"Use filters to include or restrict certain content. When selecting RPMs, be aware that package filters don't apply to modular packages."

Comment 5 Samir Jha 2023-08-15 14:43:15 UTC

Created redmine issue https://projects.theforeman.org/issues/36683 from this bug

Comment 6 Ian Ballou 2023-09-12 19:12:12 UTC

I'm changing this from an RFE to a bug because of how unclear the current workflow is. The help text telling users how modular rpms get filtered out should have been there from the start. It's not a new feature that we'll add, it's missing user context.

Comment 7 Bryan Kearney 2023-09-14 00:02:18 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36683 has been resolved.

Comment 8 Brad Buckingham 2023-10-30 11:29:29 UTC

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 14 errata-xmlrpc 2024-04-23 17:12:50 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.15.0 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-2024:2010

Note You need to log in before you can comment on or make changes to this bug.