Bug 1071767

Thanks Parag, we'll be looking. this behavior very much depends on the picked mirror and we don't do a very good job of logging that, or even logging the expected hashsums.

Thanks. I see that when I disabled all rpmfusion repo and tried again
sudo dnf clean all
sudo dnf update
it worked.

Now, I enabled rpmfusion-free-updates repo and 
$ sudo dnf clean all
Cleaning repos: puppetlabs-deps fedora rpmfusion-free-updates local updates
              : openstack-icehouse google-chrome puppetlabs-products
Cleaning up Everything

$ sudo dnf update
Puppet Labs Dependencies El 6 - x86_64           11 kB/s | 8.3 kB     00:00    
Fedora 20 - x86_64                              242 kB/s |  36 MB     02:31    
RPM Fusion for Fedora 20 - Free - Updates       146 kB/s | 189 kB     00:01    
Error: Problem with repo 'updates': Yum repo downloading error: Downloading error(s): repodata/1e3ea54da00bcfcacc4557676558e3444f54ba645306fa2df991e67e9536f0c8-comps-f20.xml.gz - Cannot download, all mirrors were already tried without success; repodata/016b4132e54b2e118c39cadcf065526b02fd5959983867c4aec90d74eeddef87-prestodelta.xml.gz - Cannot download, all mirrors were already tried without success; repodata/13ca01ab834a54c4beb25bafbb9730134039700ace8f0d2b3e9e77ea486b1090-primary.xml.gz - Cannot download, all mirrors were already tried without success


Looks like rpmfusion updates repo issue.

This is most probably a problem with the Fedora infrastructure. I just used the repoquery command (that uses yum to download the md etc.) and got:

failure: repodata/9f8d4ff9df676e8a72cc2fdc8ea69b78f1b5b5c284409c218bb7d10bae9b31f2-filelists.sqlite.bz2 from fedora: [Errno 256] No more mirrors to try.

with a list of failed mirrors following. As long as the mirrors can offer repomd.xml that at any given time points to nonexistent MD, we can not do anything. We'll add better logging to DNF but long term the infrastructure needs to improve.

Thanks. I will leave the final resolution for this bug to you.

related: bug 1073459.

Parag, can you please attach the /var/log/dnf to this bug, preferably somewhere around the error?

It looks like the issue was with yum repo base URL. When this bug found on my system, I had already enabled baseurl as listed below.

[updates]
name=Fedora $releasever - $basearch - Updates
failovermethod=priority
baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/
#metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

You can see we have moved now from http://download.fedoraproject.org to http://dl.fedorproject.org but there was no update to fedora-release about this change.

I am also attaching related dnf.log for reference here when initial problem found.

Created attachment 871471 [details]
Related dnf log

Ah I see. I was going to investigate some really weird theories here. Good, let's close this now and keep an eye on our repos. At least we bug 1073459 got discovered this way.

this worked for me also.

all i did was to change the baseurl entry to this one:

baseurl=http://dl.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/

I still get this error with f26. 

$ sudo dnf update --refresh -v
Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync
DNF version: 2.7.2
cachedir: /var/cache/dnf
Cannot download 'http://download.fedoraproject.org/pub/fedora/linux/updates/26/x86_64/': Yum repo downloading error: Downloading error(s): repodata/566add0e40836235b87ec991192d12340fafefb2b37d24e7fbae8bb92b4a8aee-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/8778df1ff8323a665276ac41b765017810e18476b2f7663888cc65a141e0d721-prestodelta.xml.xz - Cannot download, all mirrors were already tried without success; repodata/8aab93cf85a97dcf24deda23a3c3c72f83c366ff87723e52c7c24060885c77ae-primary.xml.gz - Cannot download, all mirrors were already tried without success.
Error: Failed to synchronize cache for repo 'updates'

Please can you provide files /etc/yum.repos.d/fedora*.repo

[updates]
name=Fedora 26 - x86_64 - Updates
failovermethod=priority
baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/
#baseurl=http://mirror.netcologne.de/fedora/linux/updates/26/x86_64/
#metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch
enabled=1
repo_gpgcheck=0
type=rpm
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[updates-debuginfo]
name=Fedora $releasever - $basearch - Updates - Debug
failovermethod=priority
baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/debug/
#metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f$releasever&arch=$basearch
enabled=0
repo_gpgcheck=0
type=rpm
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[updates-source]
name=Fedora $releasever - Updates Source
failovermethod=priority
baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/SRPMS/
#metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-source-f$releasever&arch=$basearch
enabled=0
repo_gpgcheck=0
type=rpm
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

Here is very simple explanation. For repo "updates" you have only one possibility in baseurl. At the time, that you experienced the problem the url was down or inaccessible. Common fedora setting uses metalink, because it returns list of urls that can be used, therefore if any server is down, others can replace the functionality. I also tried your setting, and I was unable to reproduce the problem. Please if you think, that the problem is somewhere else, don't hesitate to reopen the bug report.