Bug 660303

Summary: pup error: TB9536d0ca <string>:64:__iter__:SyntaxError: mismatched tag
Product: Red Hat Enterprise Linux 5 Reporter: Branislav Náter <bnater>
Component: pirutAssignee: James Antill <james.antill>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.6CC: bkearney, dsglaser
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-06 15:12:31 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
error log from pup application
none
Dump from pup on Red hat 5.5 client machine. none

Description Branislav Náter 2010-12-06 12:48:03 UTC
Created attachment 464975 [details]
error log from pup application

Description of problem:
Try to run Software Updater after installation. Application exit with error. See attached log.

Version-Release number of selected component (if applicable):
RHE5.6-Server-20101124.1 x86_64
pirut-1.3.28-17.el5

How reproducible:
using scenario bellow

Steps to Reproduce:
1. Install RHEL5.6
2. Register system to RHN
3. Start Software Updater application from Applications -> System Tools menu.
  
Actual results:
Error message appears. See attached file.

Expected results:
Updates are successfully downloaded and installed.

Additional info:
The issue disappear after updating system from CLI using "yum update".

Comment 1 David Glaser 2011-01-06 14:04:30 UTC
Created attachment 472060 [details]
Dump from pup on Red hat 5.5 client machine.

Comment 2 David Glaser 2011-01-06 14:06:10 UTC
I'm having the same issue on our Red Hat machines since about mid November. These machines are registered to our local Satellite, not to RHN. Though we did re-register one to RHN for testing, with the same results. 

Updating the system with 'yum update' did make the problem go away on a few machines, but when updates came out for the machines, the problem resurfaced.

Comment 3 James Antill 2011-01-06 15:12:31 UTC

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