#11646 Mirror issue with fedora 36 and fedora-modular repo
Closed: Fixed by adrian. Opened by frenaud.

Describe what you would like us to do:


On fedora 36, the fedora-modular.repo is using a metalink that provides out of date information. Dnf update fails because fedora-modular doesn't find any functional mirror.

My fedora-modular.repo contains the following:

# cat /etc/yum.repos.d/fedora-modular.repo 
[fedora-modular]
name=Fedora Modular $releasever - $basearch
#baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Modular/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-$releasever&arch=$basearch
enabled=1
countme=1
metadata_expire=7d
repo_gpgcheck=0
type=rpm
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

Output of dnf update:

# dnf update
Fedora Modular 36 - x86_64                                                                               314  B/s | 196  B     00:00    
Errors during downloading metadata for repository 'fedora-modular':
  - Status code: 404 for http://mirror.rnet.missouri.edu/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml (IP: 128.206.116.77)
  - Status code: 404 for https://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml (IP: 38.145.60.23)
  - Status code: 404 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml (IP: 18.164.93.81)
  - Status code: 404 for http://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml (IP: 38.145.60.24)
Error: Failed to download metadata for repo 'fedora-modular': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

The metalink resolves the mirrors into the following list:

<?xml version="1.0" encoding="utf-8"?>
<metalink version="3.0" xmlns="http://www.metalinker.org/" type="dynamic" pubdate="Mon, 27 Nov 2023 08:44:28 GMT" generator="mirrormanager" xmlns:mm0="http://fedorahosted.org/mirrormanager">
 <files>
  <file name="repomd.xml">
   <mm0:timestamp>1651698721</mm0:timestamp>
   <size>6697</size>
   <verification>
    <hash type="md5">5f6cc4d93eee5be1c5ce67f36dbe8c1b</hash>
    <hash type="sha1">016066313581a7f11ea7ff7bf671aa3af114bb86</hash>
    <hash type="sha256">3892566baca15dac6365e08e7f6919a0632d34b7b751e199bc1e0eb63a4302f0</hash>
    <hash type="sha512">a11aa96d2b60ef6fa056ab1cda0ced7ec36d6b4106c94033b1e284a4915c6cbc2e18b5daa47a4c3ede832b3c3bb98ef13ab55b3baea6f3de1179fea62edb70e2</hash>
   </verification>
   <resources maxconnections="1">
    <url protocol="rsync" type="rsync" location="US" preference="100">rsync://mirror.rnet.missouri.edu/fedora-enchilada/releases/36/Modular/x86_64/os/repodata/repomd.xml</url>
    <url protocol="http" type="http" location="US" preference="100">http://mirror.rnet.missouri.edu/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml</url>
    <url protocol="https" type="https" location="US" preference="99">https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml</url>
    <url protocol="https" type="https" location="US" preference="98">https://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml</url>
    <url protocol="http" type="http" location="US" preference="98">http://dl.fedoraproject.org/pub/fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml</url>
   </resources>
  </file>
 </files>
</metalink>

All the URLs are using /fedora/linux/releases/36/Modular/x86_64/os/repodata/repomd.xml but should be replaced with /archive/fedora/linux/releases/36/Modular/x86_64/os/repodata/

Note that the other repositories are working well (fedora.repo and fedora-updates.repo)

When do you need this to be done by? (YYYY/MM/DD)


As soon as possible


Should be fixed soon. Someone was running the script to move content to the archive with --directoryRe='/36/Everything' which excluded the Modular content.

I reran the script with -directoryRe=36 and it should soon work again. Maybe 60 minutes.

Metadata Update from @adrian:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata