Bug 430605

Summary: yum traceback after update "out of range integer value"
Product: [Fedora] Fedora Reporter: Mike LaPlante <mike>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: ffesti, james.antill, katzj, pmatilai, tim.lauridsen
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: 2008-02-15 21:24:15 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
pirut traceback
none
Fix yum installonly_limit to use strings and not int's none

Description Mike LaPlante 2008-01-28 23:42:52 UTC 
Description of problem:
Yum crashes no matter how you run it. "yum clean all" "yum update" "yum -h"

[root@mike ~]# yum -h
Options Error: Error parsing '0': out of range integer value

Version-Release number of selected component (if applicable):yum-3.2.10-3.fc9


How reproducible:
 updated to 3.2.10-3, ran yum.

  
Actual results:
crash!

Expected results: 
update!


Additional info:
Attached traceback output from Pirut
Comment 1 Mike LaPlante 2008-01-28 23:42:52 UTC 
Created attachment 293222 [details]
pirut traceback
Comment 2 James Antill 2008-01-29 00:08:44 UTC 
Created attachment 293224 [details]
Fix yum installonly_limit to use strings and not int's

 You have installonly_limit manually set to 0?
 Can you try applying the following patch to
/usr/lib/python2.5/site-packages/yum

 ...or just change your config to:

installonly_limit=<off>
Comment 3 Mike LaPlante 2008-01-29 13:54:47 UTC 
Setting installonly_limit=<off> fixed it. Thanks!
Comment 4 Andrew Farris 2008-02-15 21:08:46 UTC 
This would be a good thing to have commented in the yum.conf if =0 cannot be used.
Comment 5 James Antill 2008-02-15 21:24:15 UTC 
 This is fixed in 3.2.11