Bug 705071 - Yum Metadata file does not match checksum RHEL5 64bit
Summary: Yum Metadata file does not match checksum RHEL5 64bit
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Backend
Version: RHN Stable
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: rhn-dev-list
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-16 14:57 UTC by Mark Romer
Modified: 2014-01-21 06:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-18 13:03:18 UTC


Attachments (Terms of Use)

Description Mark Romer 2011-05-16 14:57:57 UTC
Description of problem:  yum update or yum install results in an error:  error was [Errno -1] Metadata file does not match checksum


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


How reproducible:  Every time, on every machine we have


Steps to Reproduce:
1.  yum update
2.  yum install (package)
3.
  
Actual results:

yum update
Loaded plugins: rhnplugin, security
rhel-x86_64-client-5                                                     | 1.4 kB     00:00     
rhel-x86_64-client-5/primary                                             | 3.3 MB     00:00     
rhel-x86_64-client-5/primary                                             | 3.3 MB     00:00     
rhel-x86_64-client-5/primary                                             | 3.3 MB     00:00     
rhel-x86_64-client-5/primary                                             | 3.3 MB     00:00     
Error: failed to retrieve repodata/7b9ccb57e462da92f225ab2694e9f511dc848b46-primary.xml.gz from rhel-x86_64-client-5
error was [Errno -1] Metadata file does not match checksum



Expected results:  yum update complete successfully


Additional info:  only seems to be happening on the 64 bit installs 32 bit RHEL5 boxes are working fine

Comment 1 Mark Romer 2011-05-18 13:02:52 UTC
Well typical RedHat again....  I checked this last night (5/17/11) before I left work and still the same problem.  This morning (5/18/11) I tried a yum update again and magically it had been fixed.  No status from RedHat on this at all.  Still floating around somewhere in Raleigh within their corporate FUD....

thanks Redhat for fixing this anyway....


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