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.
Reposync should sync the entire repository to include module information. reposync should download the packages regardless of whether a module is enabled or disabled
Description of problem:
Packages are only accessible when a specific module or stream is enabled. Reposync is not able to sync the repository because it has to abide by these rules. The workaround would be to enable all modules, sync, then switch to any alternative streams or any remaining un-enabled modules, then sync again.
This should be a simply run reposync and it syncs the entire repository without having to consider what's missing
Version-Release number of selected component (if applicable):
dnf-utils-4.0.2.2-3.el8.noarch
How reproducible:
Everytime
Steps to Reproduce:
1. reposync --disablerepo="*" --enablerepo="rhel-8-for-x86_64-appstream-rpms"
Actual results:
reposync only downloads packages that are accessible
Expected results:
reposync should download the entire repository to include modules that are not enabled or even disabled
Additional info:
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:3583
This issue appears to be present again under dnf-plugins-core-4.0.21-23.el8 @mblaha
We are experiencing the exact same behavior if the workaround you described isn't present for both ubi-8-appstream and rhel-8-for-x86_64-appstream-rpms
Currently installed:
dnf.noarch 4.7.0-19.el8 @rhel-8-for-x86_64-baseos-rpms
dnf-automatic.noarch 4.7.0-19.el8 @rhel-8-for-x86_64-baseos-rpms
dnf-data.noarch 4.7.0-19.el8 @rhel-8-for-x86_64-baseos-rpms
dnf-plugin-subscription-manager.x86_64 1.28.40-1.el8_9 @rhel-8-for-x86_64-baseos-rpms
dnf-plugins-core.noarch 4.0.21-23.el8 @rhel-8-for-x86_64-baseos-rpms
yum.noarch 4.7.0-19.el8 @rhel-8-for-x86_64-baseos-rpms
yum-utils.noarch 4.0.21-23.el8 @rhel-8-for-x86_64-baseos-rpms