Bug 454444

Summary: Crash dump against piruit occured after I selected option to review contents of Package Update
Product: [Retired] Red Hat Network Reporter: Donald Holly <dholly>
Component: RHN/ChannelsAssignee: Sebastian Skracic <sskracic>
Status: CLOSED DUPLICATE QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: RHN DevelCC: bkearney, james.antill, rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-26 17:47:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
rhel 5.2 crash dump against piruit none

Description Donald Holly 2008-07-08 15:17:03 UTC 
Description of problem: Crash dump  occured after I selected option to review 
contents of Package Updater. Screen message states: "An unhandled exception has 
occurred. This is mostly a bug. Please save the crash dump and file a detailed 
bug report against pirut at https://bugzilla.redhat.com/bugzilla".


Version-Release number of selected component (if applicable): Red Hat EL 5.2


How reproducible: Everytime I select to review Package Updates.


Steps to Reproduce:
1. Icon notice that there are updates waiting to be processed.
2. Select option to review updates
3. Crash dump notice.
  
Actual results: Crash dump.


Expected results: To see packages that can be updated.


Additional info: Had updated twice before on a fresh installation of RHEL 5.2.
Comment 1 Donald Holly 2008-07-08 15:17:03 UTC 
Created attachment 311277 [details]
rhel 5.2 crash dump against piruit
Comment 2 James Antill 2008-07-08 16:46:15 UTC 
 Well we probably could handle this better, but it also shouldn't be happening
... the actual problem is that the metadata on the RHN satellite you are talking
to is bad (or possibly some weird network thing).

    raise yum.Errors.RepoError, \
RepoError: failed to retrieve repodata/updateinfo.xml.gz from rhel-i386-server-5
error was [Errno -1] Metadata file does not match checksum

...so the updateinfo.xml.gz file doesn't match the checksum it had when the
index was generated.
Comment 3 Donald Holly 2008-07-18 18:26:33 UTC 
Do I need to re-generate the index file or does RHEL do this everytime it 
checks for new updates?
Comment 4 Sebastian Skracic 2010-08-26 17:47:06 UTC 

*** This bug has been marked as a duplicate of bug 452538 ***