Red Hat Bugzilla – Bug 206755
yum list available ( or any other action) results in "Metadata file does not match checksum". Inconsistent behavior, sometimes it works.
Last modified: 2013-01-10 05:11:24 EST
Description of problem:
Running yum on a RHEL5 Beta, registered to RHN. More often than not, yum will
fail with the message as shown in the Summary. I have seen this problem with yum
in Fedora Core [1-6] over a number of years. I think it may be due to
inconsistent cached files in a proxy, yet I am not using a proxy.
Our Hosted RHN does some form of reverse proxy yes?
Version-Release number of selected component (if applicable):
[root@unused-138 rhel-i386-server-5-beta]# rpm -qa \*yum\*
7 out of ten times, the failure occurs
Steps to Reproduce:
1. Install the Beta RHEL5
2. Register to RHN
3. Run 'yum list available'
# yum list available
Setting up repositories
rhel-i386-server-5-beta 100% |=========================| 672 B 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 504 kB 00:01
[Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/primary.xml.gz from rhel-i386-server-5-beta: [Errno
256] No more mirrors to try.
A list of packages available returned by yum.
Because there are multiple physical machines serving up the repodata files, and
because gziped files may contain a timestamp, the files served from each machine
have identical content, but different checksums. The fix will be to not include
a timestamp on the compressed files.
This appears to be working with
talking to RHN414. Tested in stage environment.
*** Bug 208547 has been marked as a duplicate of this bug. ***
Verified in prod with