Cause:
The Content View publish process copies all modules irrespective of any filters. However, the RPMs belonging to these module are subject to package filtering.
Consequence:
A Content View publish action will copy all modules and any RPMs included by a filter, but not RPMs excluded by a filter, even if the excluded RPMs are required by a module.
Workaround (if any):
Check for the RPMs belonging to a module to be used in a Content View and include the modules RPMs in the Content View. Consider using Composite Content Views with modules your require in separate Content Views for ease of management.
Result:
A module's presence in a Content View will allow the module stream to be enabled, but some RPMs might not be present due to package filtering.
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.
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
Comment 13Red Hat Bugzilla
2023-09-14 05:25:24 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days