Bug 1643281 - dnf does not try other mirrors if the current mirror fails when downloading a package
Summary: dnf does not try other mirrors if the current mirror fails when downloading a...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-25 19:43 UTC by clime
Modified: 2019-05-28 23:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:57:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dnf.log (222.94 KB, text/plain)
2018-10-25 19:45 UTC, clime
no flags Details
dnf.librepo.log (43.62 KB, text/plain)
2018-10-25 19:49 UTC, clime
no flags Details

Description clime 2018-10-25 19:43:42 UTC
Description of problem:

If dnf is downloading a package and the downloading suddenly starts to fail with 503 service unavailable error, then dnf does not retry to download the package from next mirror. It immediately fails with ''No more mirrors to try - All mirrors were already tried without success' message. But according to logs, it did not actually try any other mirrors. It just immediately failed with this message after getting 10x 503 on just that first mirror it was downloading a package from.


The original issue is reported here https://bugzilla.redhat.com/show_bug.cgi?id=1638048

Related issue with more info is filed here: https://pagure.io/fedora-infrastructure/issue/7301

I will add dnf.log and dnf.librepo.log for one such failed download occurrence.


Version-Release number of selected component (if applicable):
dnf 2.7.5


How reproducible:
when doing rebuilds of packages in https://copr.fedorainfracloud.org/coprs/mkyral/plasma-unstable/

Steps to Reproduce:
1. simulate 503 during package download with multiple repos returned by mirrorlink
2.
3.

Actual results:
dnf tries 10x the same mirror and then dies


Expected results:
dnf retries the package download with next mirror in the mirrolist


Additional info:

Comment 1 clime 2018-10-25 19:45:33 UTC
Created attachment 1497562 [details]
dnf.log

Comment 2 clime 2018-10-25 19:49:28 UTC
Created attachment 1497563 [details]
dnf.librepo.log

Comment 3 Ben Cotton 2019-05-02 19:38:41 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-28 23:57:19 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.