Bug 638922 - Pup/Pirut/etc. crash due to RHN: Metadata file does not match checksum
Summary: Pup/Pirut/etc. crash due to RHN: Metadata file does not match checksum
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Channels
Version: RHN Stable
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Sebastian Skracic
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard:
: 638958 639047 639657 639731 641149 644723 663419 663488 667185 667271 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-30 11:43 UTC by jzh
Modified: 2013-01-10 10:44 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-15 12:15:22 UTC
Embargoed:


Attachments (Terms of Use)
what was dumped by the application when it crashed (1.76 KB, text/plain)
2010-09-30 11:43 UTC, jzh
no flags Details
dump file from pup (1.72 KB, text/plain)
2011-01-05 19:06 UTC, Jamie Shaffer
no flags Details

Description jzh 2010-09-30 11:43:00 UTC
Created attachment 450736 [details]
what was dumped by the application when it crashed

Description of problem:

The program crashed and requested that I file a report, so here I am doing so. As for these details, I've little idea. just trying to be diligent and help, whilst having a million and one other things to do ...

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Panu Matilainen 2010-09-30 13:14:18 UTC
Reassigning to the crashing component, rpm isn't involved here. Whether its actually yum or pirut that's failing to catch the RepoError exception I dunno...

Comment 2 James Antill 2010-09-30 13:48:21 UTC
RepoError: failed to retrieve repodata/208e0e2bcdbffac4b526cb79a5e4e7252382a953-updateinfo.xml.gz from rhel-i386-server-5
error was [Errno -1] Metadata file does not match checksum

Comment 3 James Antill 2010-09-30 13:57:48 UTC
*** Bug 638958 has been marked as a duplicate of this bug. ***

Comment 4 James Antill 2010-10-01 14:34:43 UTC
*** Bug 639047 has been marked as a duplicate of this bug. ***

Comment 5 James Antill 2010-10-04 11:59:00 UTC
*** Bug 639657 has been marked as a duplicate of this bug. ***

Comment 6 James Antill 2010-10-04 12:10:24 UTC
*** Bug 639731 has been marked as a duplicate of this bug. ***

Comment 7 Sebastian Skracic 2010-10-05 15:42:16 UTC
I was not able to reproduce the behavior reported -- all attempts to download the said updateinfo.xml.gz file yielded complete and successful download.  I believe it was a transient event, probably a network glitch between RHN origin and Akamai caching layer.  But -- as I said already, this is just a guess.

Please reopen if it happens again.

Comment 8 James Antill 2010-10-07 21:48:36 UTC
*** Bug 641149 has been marked as a duplicate of this bug. ***

Comment 12 James Antill 2010-10-20 13:35:09 UTC
*** Bug 644723 has been marked as a duplicate of this bug. ***

Comment 13 James Antill 2010-12-15 19:12:37 UTC
*** Bug 663419 has been marked as a duplicate of this bug. ***

Comment 14 James Antill 2010-12-16 06:21:10 UTC
*** Bug 663488 has been marked as a duplicate of this bug. ***

Comment 15 Rolf Kyburz 2010-12-17 09:03:11 UTC
I had the problem, and it persisted even after the bug was allegedly corrected - however, after a "yum clean all" (which did *not* help when the bug was still there), "pup" now ran without error messages.

Comment 16 James Antill 2011-01-04 19:24:18 UTC
*** Bug 667185 has been marked as a duplicate of this bug. ***

Comment 17 James Antill 2011-01-05 18:33:25 UTC
*** Bug 667271 has been marked as a duplicate of this bug. ***

Comment 18 James Antill 2011-01-05 18:34:31 UTC
I'm going to reopen this bug, given that I've now closed another 4 duplicates against it in the last month.

Comment 19 Jamie Shaffer 2011-01-05 19:06:16 UTC
Created attachment 471926 [details]
dump file from pup

Comment 20 Jamie Shaffer 2011-01-05 19:07:36 UTC
This bug seemed to disappear (fixed?) in December, but has reappeared today on 2 of 4 machines when trying to update with pup. I tried "yum clean all" and "rhn-profile-sync" and even rebooting. Still crashing.

Comment 21 Sebastian Skracic 2011-01-06 10:02:35 UTC
I have manually refreshed rhel-x86_64-client-5/ba8760ec617fcc56f04856fab8c68557615feb38-updateinfo.xml.gz.  It should no longer be corrupted.

I propose we leave this BZ open to consolidate all CDN repodata corruption reports in single place.

Comment 22 Sebastian Skracic 2011-12-15 12:15:22 UTC
Closing this bug since we have a) identified the root cause of the issues in the networking stack b) assembled a process that helps us diagnose and act proactively on this kind of issues in the future.

As always, if the need arises, I suggest everyone involved to file a new BZ if this problem pops up again.


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