Failed to synchronize cache for repo 'fedora-modular'

Project Discussion
1

Is there a fix/workaround for the following dnf repo synchronization failure?

:small_blue_diamond:[ptrber@toolbox ~]$ sudo dnf update -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.2.2
cachedir: /var/cache/dnf
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
ā€¦
repo: downloading from remote: fedora-modular
error: Curl error (6): Couldnā€™t resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] (https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64).
Fedora Modular 30 - x86_64 0.0 B/s | 0 B 00:20
Cannot download ā€˜https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64ā€™: Cannot prepare internal mirrorlist: Curl error (6): Couldnā€™t resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org].
Failed to synchronize cache for repo ā€˜fedora-modularā€™
Error: Failed to synchronize cache for repo ā€˜fedora-modularā€™

2

Are you using the toolbox from the repo or the latest version from github?

I had the same issue yesterday using the most recent toolbox commit (de67ff4bcc09a4d667943bbae1a98d34d3de9f1d). The one from the repo worked for me.

3

Hey, Iā€™ve got the same problem. Running the latest version available in the repos.

4

That is strange.

When I create a new container using the toolbox from github ./toolbox create -c testcontainer and then enter it using ./toolbox enter --container testcontainer I can neither use ssh nor dnf.

Doing the same with the shipped (SB 30.20190427.n.0) version of toolbox (toolbox create -c testcontainer2 && toolbox enter --container testcontainer2), everything works well. Even when I use the github version just for entering the container, everything works. So I think it has something to do with the way containers are created.

5

Hmm might be that the base image changed, maybe by accident, out of curiosity would microdnf happen to work inside?

You might also want to look into a bug report, maybe also try passing -v and --candidate-registry.

6

Thanks for the hint, but the result is the same. However, I removed two lines from the toolbox script and the containers created now have network connection again.

diff --git a/toolbox b/toolbox
index 4f3463f..884bdcc 100755
--- a/toolbox
+++ b/toolbox
@@ -938,13 +938,11 @@ create()
 
     # shellcheck disable=SC2086
     $prefix_sudo podman create \
-            $dns_none \
             $toolbox_path_set \
             --group-add wheel \
             --hostname toolbox \
             --name $toolbox_container \
             --network host \
-            $no_hosts \
             --pid host \
             --privileged \
             --security-opt label=disable \

Can someone confirm that? If so, we should file a bug report.

7

Ah yeah that definitely seems like a bug, thatā€™s a rather new change in an effort to keep your resolv.conf in sync with the host system.

8

@ludwigd, @refi64, @jurf - thanks for looking into this.

Using the shipped version of toolbox (SB version 30.20190507.1) . It is working again and I can not replicate the synchronization failure.

9

Itā€™s now working for me too, cheers all!

10

ā€¦and today it is not working againā€¦
What is going on here?
:small_blue_diamond:[ptrber@toolbox ~]$ sudo dnf update -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.2.2
cachedir: /var/cache/dnf
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
error: Curl error (6): Couldnā€™t resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] (https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64).
Fedora Modular 30 - x86_64 0.0 B/s | 0 B 00:10
Cannot download ā€˜https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64ā€™: Cannot prepare internal mirrorlist: Curl error (6): Couldnā€™t resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-30&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org].
Failed to synchronize cache for repo ā€˜fedora-modularā€™
Error: Failed to synchronize cache for repo ā€˜fedora-modularā€™

Today it happened when I need to work to meet a deadline. Not goodā€¦
Looks like I have to leave Silverblue for a while.

1 Like
11

Same problem at fresh install. Cannot update or install apps.
[immjke@localhost ~]$ sudo dnf update -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.2.2
cachedir: /var/cache/dnf
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id ā€œfailovermethodā€ does not exist
repo: using cache for: fedora-modular
not found other for: Fedora Modular 30 - x86_64
not found deltainfo for: Fedora Modular 30 - x86_64
not found updateinfo for: Fedora Modular 30 - x86_64
fedora-modular: using metadata from Fri 26 Apr 2019 02:47:30 AM MSK.
repo: downloading from remote: updates-modular
error: Curl error (52): Server returned nothing (no headers, no data) for https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck [Empty reply from server] (https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck).
error: Curl error (52): Server returned nothing (no headers, no data) for https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck [Empty reply from server] (https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck).
error: Zchunk header checksum didnā€™t match expected checksum (http://www.nic.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck).
error: Zchunk header checksum didnā€™t match expected checksum (http://www.nic.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck).
Fedora Modular 30 - x86_64 - Updates 421 kB/s | 875 kB 00:02
Cannot download ā€˜https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f30&arch=x86_64ā€™: Checksum error /var/cache/dnf/updates-modular-783da5de2e38c644/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck: Unable to read zchunk lead.
Failed to synchronize cache for repo ā€˜updates-modularā€™
Error: Failed to synchronize cache for repo ā€˜updates-modularā€™

12

@ptrber, @immjke What about the general connectivity of the toolbox? Does everything else work (ssh, wget, etc) or is it just the repo that does not sync?

13 
sudo dnf update -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.2.2
cachedir: /var/cache/dnf
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
repo: using cache for: fedora-modular
not found other for: Fedora Modular 30 - x86_64
not found deltainfo for: Fedora Modular 30 - x86_64
not found updateinfo for: Fedora Modular 30 - x86_64
fedora-modular: using metadata from Thu 25 Apr 2019 11:47:30 PM UTC.
repo: downloading from remote: updates-modular
error: Downloading successful, but checksum doesn't match. Calculated: 19681c5615cb30a94e569f2a3e743e5b74a3ac4c5966026fff54050e55af377addb3809710363328cbe8a4bd7887ce892f0051463eafa597e5a992b2555751f5(sha512) 19681c5615cb30a94e569f2a3e743e5b74a3ac4c5966026fff54050e55af377addb3809710363328cbe8a4bd7887ce892f0051463eafa597e5a992b2555751f5(sha512)  Expected: 0d18861765a9cbfe43285a54e205bc1e636602823bb533f67f5abed0326df32a1311cb78197c2e5b6102f6b982aac0876616e249a966e857d0147dc3e1c2d874(sha512) 512d5b4545c9cc72f803a88e83e62b7c35b8a1b792c2d8106cf08bbf99aec31fec1399865d5be1348da1b05cb43f8645b53187e56b3b10281722f8d9b16ff41e(sha512)  (https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/repomd.xml).
error: Downloading successful, but checksum doesn't match. Calculated: 19681c5615cb30a94e569f2a3e743e5b74a3ac4c5966026fff54050e55af377addb3809710363328cbe8a4bd7887ce892f0051463eafa597e5a992b2555751f5(sha512) 19681c5615cb30a94e569f2a3e743e5b74a3ac4c5966026fff54050e55af377addb3809710363328cbe8a4bd7887ce892f0051463eafa597e5a992b2555751f5(sha512)  Expected: 0d18861765a9cbfe43285a54e205bc1e636602823bb533f67f5abed0326df32a1311cb78197c2e5b6102f6b982aac0876616e249a966e857d0147dc3e1c2d874(sha512) 512d5b4545c9cc72f803a88e83e62b7c35b8a1b792c2d8106cf08bbf99aec31fec1399865d5be1348da1b05cb43f8645b53187e56b3b10281722f8d9b16ff41e(sha512)  (http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/repomd.xml).
error: Status code: 404 for https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck (https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck).
error: Status code: 404 for https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck (https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck).
error: Status code: 404 for https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/e869b2aca53924688ec822b892538dcc7d74cec6ba3d108604f450ae86c1ffb8-modules.yaml.gz (https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/e869b2aca53924688ec822b892538dcc7d74cec6ba3d108604f450ae86c1ffb8-modules.yaml.gz).
error: Status code: 404 for http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck (http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck).
error: Status code: 404 for http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/e869b2aca53924688ec822b892538dcc7d74cec6ba3d108604f450ae86c1ffb8-modules.yaml.gz (http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/e869b2aca53924688ec822b892538dcc7d74cec6ba3d108604f450ae86c1ffb8-modules.yaml.gz).
error: Status code: 404 for http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/a4545d783e52f4e13c75db8f88f87f299106931d8c46711974ba891db537b03c-updateinfo.xml.xz (http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/a4545d783e52f4e13c75db8f88f87f299106931d8c46711974ba891db537b03c-updateinfo.xml.xz).
error: Curl error (52): Server returned nothing (no headers, no data) for https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck [Empty reply from server] (https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck).
error: Status code: 404 for https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/a4545d783e52f4e13c75db8f88f87f299106931d8c46711974ba891db537b03c-updateinfo.xml.xz (https://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/a4545d783e52f4e13c75db8f88f87f299106931d8c46711974ba891db537b03c-updateinfo.xml.xz).
error: Zchunk header checksum didn't match expected checksum (http://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/9bb278c48d73a3fe356fd255177f55a7900c4d598e7aa96f1b192aaba2406ce8-filelists.xml.zck).
error: Status code: 404 for http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck (http://mirror.linux-ia64.org/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck).
error: Curl error (52): Server returned nothing (no headers, no data) for https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck [Empty reply from server] (https://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck).
error: Zchunk header checksum didn't match expected checksum (http://mirror.yandex.ru/fedora/linux/updates/30/Modular/x86_64/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck).
Fedora Modular 30 - x86_64 - Updates                                                                                                                                               269 kB/s | 877 kB     00:03    
Cannot download 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f30&arch=x86_64': Checksum error /var/cache/dnf/updates-modular-783da5de2e38c644/repodata/f850ebe08c1f80a08866f62242b0e6a7091e500ef2a205bd3dc1c16640f06f1c-primary.xml.zck: Unable to read zchunk lead.
Failed to synchronize cache for repo 'updates-modular'
Error: Failed to synchronize cache for repo 'updates-modular'
14

Sometimes it works, sometimes it doesnā€™t. I still do not understand what it depends on.

15

This has been fixed in the latest librepo release. See 1706321 ā€“ Issues with Fedora 30 mirrors - files missing(?) or corrupted for more details.