Bug 1940721

Summary: Dnf failed with Zchunk error at the first mirror from mirrorlist and won't try next
Product: [Fedora] Fedora Reporter: Robin Lee <robinlee.sysu>
Component: dnfAssignee: amatej
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: amatej, dmach, jmracek, jrohel, liusen, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame, vpeltola
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-29 11:11:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robin Lee 2021-03-19 01:30:45 UTC
Description of problem:
I get zchunk errors recently. Is that caused by bad mirror? Can dnf skip the bad mirror and try next to fetch the needed file?
A few hour later the issue will disappear.

sudo dnf -v --releasever=34 --setopt=module_platform_id=platform:f34      --enablerepo=updates-testing --enablerepo=updates-testing-modular      distro-sync
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync, system-upgrade
DNF version: 4.5.2
cachedir: /var/cache/dnf
User-Agent: constructed: 'libdnf (Fedora 32; workstation; Linux.x86_64)'
repo: using cache for: adobe-linux-x86_64
adobe-linux-x86_64: using metadata from Wed 25 Nov 2020 07:51:20 AM CST.
repo: using cache for: fedora-cisco-openh264
fedora-cisco-openh264: using metadata from Tue 23 Feb 2021 08:49:00 AM CST.
repo: using cache for: fedora-modular
fedora-modular: using metadata from Thu 18 Mar 2021 06:08:11 PM CST.
repo: using cache for: updates-modular
updates-modular: using metadata from Wed 21 Feb 2018 03:18:14 AM CST.
repo: downloading from remote: updates-testing-modular
countme: no event for updates-testing-modular: window already counted
error: Zchunk error: Unable to find multipart download range                                     ] 438 kB/s | 163 kB     00:01 ETA
 (https://mirror.sjtu.edu.cn/fedora/linux/updates/testing/34/Modular/x86_64/repodata/fb8da8154909a3a3b87275b58872c394e23d10bdd3a7d5cdacce0608e17fbbe0-primary.xml.zck).
Fedora Modular 34 - x86_64 - Test Updates                                                          231 kB/s | 163 kB     00:00    
Errors during downloading metadata for repository 'updates-testing-modular':
  - Zchunk error: Unable to find multipart download range

Error: Failed to download metadata for repo 'updates-testing-modular': Yum repo downloading error: Downloading error: Unable to initialize zchunk file repodata/fb8da8154909a3a3b87275b58872c394e23d10bdd3a7d5cdacce0608e17fbbe0-primary.xml.zck: Unable to set zchunk file descriptor for repodata/fb8da8154909a3a3b87275b58872c394e23d10bdd3a7d5cdacce0608e17fbbe0-primary.xml.zck: Unable to find multipart download range

Version-Release number of selected component (if applicable):
dnf-4.5.2-1.fc32.noarch
librepo-1.12.1-1.fc32.x86_64
Also met the same issue on F33.

How reproducible:
Not always.

Steps to Reproduce:
1. dnf update, or any other similar command
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Liu Sen 2021-04-01 01:35:25 UTC
This issue can't reproduce manually, but it's of frequent occurrence.

Comment 2 vpeltola 2021-04-28 16:52:45 UTC
Same error here on Fedora 33, and now on F34 after upgrading yesterday.
Starts happening sporadically when doing a "sudo dnf update", but can go away a few hours later.  I am using a proxy setting in /etc/dnf/dnf.conf.
This error seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=1706627 and the workaround given there solves the issue, i.e. adding "zchunk=False" to /etc/dnf/dnf.conf file.

Comment 3 amatej 2021-04-29 11:11:21 UTC
Based on the reports I believe this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1927988

*** This bug has been marked as a duplicate of bug 1927988 ***