Bug 1737160

Summary:	dnf in beta barfs on zck files
Product:	Red Hat Enterprise Linux 8	Reporter:	Stephen John Smoogen <smooge>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	fweimer, james.antill, mdomonko
Target Milestone:	rc
Target Release:	8.0
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:	2019-08-05 11:52:33 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 Stephen John Smoogen 2019-08-02 22:53:56 UTC

Description of problem:

dnf will fail when it comes to a repository which has a .zck (zchunk) file in its metadata. While this should only occur for Fedora30+ repos, it can occur in other ones. The version of dnf in 8.0 does not fail when it sees a file like this

Version-Release number of selected component (if applicable):
dnf-4.2.6-1.el8.noarch
dnf-4.2.7-2.el8.noarch

dnf-4.0.9.2-5.el8.noarch works

How reproducible:
100%

Steps to Reproduce:
1. install RHEL-8.1
2. download and install epel-release from dl.fedoraproject.org/pub/epel/
3. yum update

Actual results:

[root@rhel8-1 log]# yum update
Updating Subscription Management repositories.
Extra Packages for Enterprise Linux 8 - x86_64                                                                26 kB/s |  16 kB     00:00    
failed to open: /var/cache/dnf/epel-fafd94c310c51e1e/repodata/40b4c616fff77d0865d318d14dbd46da0906f3a9c1a1de521a7f57d2109a4d4d-updateinfo.xml.zck


Expected results:


Additional info:

Comment 1 Michal Domonkos 2019-08-05 11:52:33 UTC


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