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.
DescriptionWilliam Cody Laeder
2021-10-01 22:03:30 UTC
Created attachment 1828185[details]
The error we observe
Description of problem:
Older version of `reposync` would continue on
Version-Release number of selected component (if applicable):
Appears recreatable on all `dnf reposync` versions.
How reproducible:
Trivial, like clockwork.
Steps to Reproduce:
1. Setup a valid repo with at least 2 packages.
2. Make it available over HTTPS
3. Setup at least 2 basic auth users
4. Allow the first basic auth user to download both packages
5. Set the second basic auth user to only download 1 package
6. Perform a `dnf reposync` with the second user
Actual results:
reposync will fail with an error
Expected results:
Prior versions of reposync would cleanly exit.
Additional info:
Thanks for reporting this. Reposync command unfortunately uses librepo's LR_PACKAGEDOWNLOAD_FAILFAST flag resulting in cancelling the packages download after the first irrecoverable error.
Just to be sure - does the traceback in the attachment come from dnf.log or from the console?
Hm, that's strange - have you overridden the default debuglevel? Either using config option `debuglevel=<level>` in /etc/dnf/dnf.conf or using command line switch --debuglevel=<level>.
Comment 6William Cody Laeder
2021-10-11 16:30:40 UTC
> Hm, that's strange - have you overridden the default debuglevel?
Yes `debuglevel=` was set to its maximum within `/etc/dnf/dnf.conf`
Thanks in that case the traceback on the terminal is expected. We write the traceback to the log file and in case the `debuglevel` is set to high value, it's also printed on console.
Comment 14William Cody Laeder
2021-12-10 19:16:28 UTC
Is there a work around?
Something that can be set in the environment/cli to override the FASTFAIL setting?
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 (dnf-plugins-core bug fix and enhancement update), 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/RHBA-2022:2052
Created attachment 1828185 [details] The error we observe Description of problem: Older version of `reposync` would continue on Version-Release number of selected component (if applicable): Appears recreatable on all `dnf reposync` versions. How reproducible: Trivial, like clockwork. Steps to Reproduce: 1. Setup a valid repo with at least 2 packages. 2. Make it available over HTTPS 3. Setup at least 2 basic auth users 4. Allow the first basic auth user to download both packages 5. Set the second basic auth user to only download 1 package 6. Perform a `dnf reposync` with the second user Actual results: reposync will fail with an error Expected results: Prior versions of reposync would cleanly exit. Additional info: