[Rpm-maint] [rpm-software-management/rpm] "Couldn't resolve host name" for a mirror is a fatal error when it should just try next mirror (Issue #3870)

[minfrin]

minfrin created an issue (rpm-software-management/rpm#3870)

**Describe the bug**
When dnf connects to a mirror, and the mirror does not exist in the DNS, the whole transfer fails. What should happen instead is the mirror must be avoided and the next mirror tried.

**To Reproduce**
Steps to reproduce the behavior:
1. Have a mirror in the mirror list whose name does not exist in DNS
2. Run "dnf update"
3. Fatal error, dnf gives up.

**Expected behavior**
When a mirror fails because the DNS name was not found, the next mirror must be tried.

**Output**

created by dnf config-manager from https://rpm.librewolf.net                                                                                                                                    0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'rpm.librewolf.net':
  - Curl error (6): Couldn't resolve host name for https://rpm.librewolf.net/repodata/repomd.xml [Could not resolve host: rpm.librewolf.net]
Error: Failed to download metadata for repo 'rpm.librewolf.net': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

**Environment**
 - OS / Distribution: Rocky9
 - Version: dnf-4.14.0-25.el9.noarch



-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3870
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3870 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20250727/13633b5e/attachment.htm>