Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 402991 - yum metadata groupupdate checksum broken
yum metadata groupupdate checksum broken
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Fedora Extras Quality Assurance
: 345051 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2007-11-28 10:30 EST by Trevor Cordes
Modified: 2014-01-21 18:00 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-28 10:39:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Trevor Cordes 2007-11-28 10:30:34 EST
Description of problem:
Something broke the F8 groupupdate yum checksums.  Can't yum groupupdate Base on
any F8 box.  I tried all the steps google suggest for this error.  This bug has
been reproduced on 3 boxes, one of which ran groupupdate ok just the other day.

Version-Release number of selected component (if applicable):

How reproducible:
always, 3 boxes tested so far

Steps to Reproduce:
1. yum clean all
2. yum groupupdate Base
Actual results:
Loading mirror speeds from cached hostfile
comps-f8.xml              100% |=========================| 1.2 MB    00:01     
[Errno -1] Metadata file does not match checksum
Trying other mirror.
comps-f8.xml              100% |=========================| 1.2 MB    00:01     
[Errno -1] Metadata file does not match checksum
Trying other mirror.
comps-f8.xml              100% |=========================| 1.2 MB    00:01     
[Errno -1] Metadata file does not match checksum
Trying other mirror.

Expected results:
yum should update without checksum errors

Additional info:
yum update appears to run fine, it's just the groupupdate that fails.  Tried
with and without yum-fastestmirror.  Tried clearing all proxy caches.  Tried
flushing data/metadata many times.
Comment 1 Jesse Keating 2007-11-28 10:39:54 EST
THere was a corrupted comps file in the repo.  This was corrected yesterday, if
your mirror is up to date you should no longer be seeing this issue.
Comment 2 Seth Vidal 2007-12-06 22:36:05 EST
*** Bug 345051 has been marked as a duplicate of this bug. ***

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