Red Hat Bugzilla – 1713780 – Many packages are not accessible until a module is enabled. There is no way to search what module a package is in without first having the module enabled which is counter intuitive
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Many packages are not accessible until a module is enabled. There is no way to search what module a package is in without first having the module enabled which is counter intuitive
Description of problem:
*With no modules enabled:*
yum module list --enabled
No matching Modules to list
# yum repolist
repo id repo name status
codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady L 1,479
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise 4,230
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise 1,965
*With all modules enabled:*
yum module list --disabled
No matching Modules to list
yum repolist
repo id repo name status
codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady L 2,041
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise 5,200
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise 1,963
___
CodeReady goes up by 562 packages, appstream goes up by almost 1000, and baseos goes down by 2.
Why wouldn't a customer be able to access every package regardless of the module being enabled or disabled. Packages can be installed separately from their modules.
There is no way to query a package and find out what module its in unless that module is already enabled. repoquery and yum will just report that the package cannot be found.
Why did baseos go down in packages from me enabling all the modules (just the default streams, If no default, then the only stream). Why don't all modules have a default stream? Should I address that with a bugzilla against each module?
Expected results:
Packages should be installable regardless of a module being enabled or disabled. You can install the packages of a module without even enabling a
Additional info: