Bug 1574425 - rpm-ostree failed because bad checksum of repomd.xml
Summary: rpm-ostree failed because bad checksum of repomd.xml
Alias: None
Product: Fedora
Classification: Fedora
Component: atomic
Version: 28
Hardware: powerpc
OS: Unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-03 09:39 UTC by Michel Normand
Modified: 2018-05-03 12:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-03 12:44:42 UTC
Type: Bug

Attachments (Terms of Use)
etc_yum_repos_d_all_cat.log (4.94 KB, patch)
2018-05-03 09:40 UTC, Michel Normand
no flags Details | Diff

Description Michel Normand 2018-05-03 09:39:09 UTC
rpm-ostree failed because bad checksum of repomd.xml

start a guest with qcow2 from

$rpm-ostree install jq
Checking out tree 1c1013e... done
Enabled rpm-md repositories: updates fedora
Updating metadata for 'updates': 100%
rpm-md repo 'updates'; generated: 2018-05-02 10:13:54
error: cannot update repo 'fedora': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried; Last error: Downloading successful, but checksum doesn't match. Calculated: 5f8693c7e4bf2973d3c6561a473bcdf8e79f9e0d3f96f024fa01c6da3851d096a882927b6b833302d072c0a369a7b89f9078f01ea20cce974518fa887a3b7b4c(sha512)  Expected: b643df69c8743da93b0a6e9a640b4141a103ff3517cbdade1fd1298b392e156a2a94aea483007cb52191a03712302d6aa7d0d7ee6c8c3a2d51031f24b944438f(sha512) 

I manually retrieved the /etc/yum_repos.d/* in attached file

Comment 1 Michel Normand 2018-05-03 09:40:26 UTC
Created attachment 1430569 [details]

Comment 3 Michel Normand 2018-05-03 09:59:39 UTC
There is no such failure with qcow2 from 20180501 compose.

Comment 4 Colin Walters 2018-05-03 12:44:42 UTC
The way Fedora manages RPM metadata today is simply full of race conditions.  This is nothing new, you just need to try again later unfortunately.

Someday we'll fix this hopefully.

Note You need to log in before you can comment on or make changes to this bug.