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.
Bug 2009894 - dnf reposync does not continue on 401 errors
Summary: dnf reposync does not continue on 401 errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf-plugins-core
Version: 8.4
Hardware: All
OS: Linux
medium
unspecified
Target Milestone: rc
: ---
Assignee: Marek Blaha
QA Contact: Jan Blazek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-01 22:03 UTC by William Cody Laeder
Modified: 2022-05-10 16:41 UTC (History)
3 users (show)

Fixed In Version: dnf-plugins-core-4.0.21-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:23:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
The error we observe (2.37 KB, text/plain)
2021-10-01 22:03 UTC, William Cody Laeder 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-98703 0 None None None 2021-10-01 22:03:58 UTC
Red Hat Product Errata RHBA-2022:2052 0 None None None 2022-05-10 15:24:00 UTC

Description William 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:
Comment 1 Marek Blaha 2021-10-06 05:36:30 UTC 
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?
Comment 3 Marek Blaha 2021-10-06 12:05:36 UTC 
Here are patches fixing the issue: https://github.com/rpm-software-management/dnf/pull/1790, https://github.com/rpm-software-management/dnf-plugins-core/pull/440

And here is PR with test: https://github.com/rpm-software-management/ci-dnf-stack/pull/1044/files
Comment 4 William Cody Laeder 2021-10-08 21:21:32 UTC 
> Just to be sure - does the traceback in the attachment come from dnf.log or from the console?


That was from the terminal/consul output
Comment 5 Marek Blaha 2021-10-11 08:44:39 UTC 
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 6 William 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`
Comment 7 Marek Blaha 2021-10-12 05:36:56 UTC 
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 14 William 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?
Comment 16 errata-xmlrpc 2022-05-10 15:23:48 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.