Consider a content view that has repositories with modules streams . As of Sat 6.5 the Content View publish process copies over all the modules irrespective of any filters. However the rpms belonging to these module streams (aka Modular Rpms) are subject to the regular package filtering. This causes the module streams in the resulting content view environment to be in a semi-broken (aka ursine) state. For example: Consider a content view with a repo that has a Module Stream M, and modular rpms R1 and R2 belonging to M. Assume this repo also has a non modular rpm N. If this content view had a package filter that says "Include only rpm N". The content view publish will copy over module stream M and rpm N but will ignore R1 and R2. This could lead to a dubious CVE where the customer enables the module stream but is not able to install the rpms belonging to this. We need to mark rpms belonging to module streams as "modular" and have them evade the filtering process and automatically copied over. We need to limit the filtering to only non modular rpms. Version-Release number of selected component (if applicable): 6.5 nightly Steps to Reproduce: 1) Create a content view 2) Add a repo with module streams 3) Create an includes filter that says "Include foo" (where is foo is a non modular rpm.) 4) Publish the content view Expected: All modules streams and modular rpms get copied over in addtion to what you have for the include. Actual: Notice that all the module streams got copied over. However only foo got copied over in terms of rpms.
Connecting redmine issue https://projects.theforeman.org/issues/26223 from this bug
Connecting redmine issue https://projects.theforeman.org/issues/26221 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26223 has been resolved.
Verified this in Satellite 6.5 with Snap 22, everything works fine. Executed all Scenarios mentioned as https://github.com/Katello/katello/pull/8014#issuecomment-477068810
Created attachment 1553831 [details] attaching filtering result
Marking this ticket as verified, as per my above comment
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, 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-2019:1222
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days