This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 974713 - [abrt] yum-3.4.3-54.fc18: int() argument must be a string or a number, not 'NoneType'
[abrt] yum-3.4.3-54.fc18: int() argument ...
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-06-14 18:46 EDT by Brian Morrison
Modified: 2014-02-05 16:49 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-02-05 16:49:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (2.85 KB, text/plain)
2013-06-14 18:46 EDT, Brian Morrison
no flags Details
File: core_backtrace (1.88 KB, text/plain)
2013-06-14 18:46 EDT, Brian Morrison
no flags Details
File: environ (1.93 KB, text/plain)
2013-06-14 18:46 EDT, Brian Morrison
no flags Details

  None (edit)
Description Brian Morrison 2013-06-14 18:46:13 EDT
Description of problem:
I rebooted my system after various updates including kernel-3.9.5-201

This problem started on the attempted run of sudo yum check-update

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.4
cmdline:        /usr/bin/python /bin/yum makecache
executable:     /bin/yum
kernel:         3.9.5-201.fc18.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace: int() argument must be a string or a number, not 'NoneType'

Traceback (most recent call last):
  File "/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/", line 319, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/", line 144, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/", line 485, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/", line 1192, in doCommand
  File "/usr/lib/python2.7/site-packages/yum/", line 138, in doSetup
  File "/usr/lib/python2.7/site-packages/yum/", line 84, in retrieveAllMD
    dl = repo._async and repo._commonLoadRepoXML(repo)
  File "/usr/lib/python2.7/site-packages/yum/", line 1412, in _commonLoadRepoXML
    result = self._getFileRepoXML(local, text)
  File "/usr/lib/python2.7/site-packages/yum/", line 1190, in _getFileRepoXML
    size=102400) # setting max size as 100K
  File "/usr/lib/python2.7/site-packages/yum/", line 990, in _getFile
    result = self.grab.urlgrab(misc.to_utf8(relative), local,
  File "/usr/lib/python2.7/site-packages/yum/", line 665, in <lambda>
    grab = property(lambda self: self._getgrab())
  File "/usr/lib/python2.7/site-packages/yum/", line 660, in _getgrab
  File "/usr/lib/python2.7/site-packages/yum/", line 625, in _setupGrab
    urls = self.urls
  File "/usr/lib/python2.7/site-packages/yum/", line 845, in <lambda>
    urls = property(fget=lambda self: self._geturls(),
  File "/usr/lib/python2.7/site-packages/yum/", line 842, in _geturls
  File "/usr/lib/python2.7/site-packages/yum/", line 788, in _baseurlSetup
  File "/usr/lib/python2.7/site-packages/yum/", line 885, in <lambda>
    metalink_data = property(fget=lambda self: self._getMetalink(),
  File "/usr/lib/python2.7/site-packages/yum/", line 872, in _getMetalink
    self._metalink = metalink.MetaLinkRepoMD(result)
  File "/usr/lib/python2.7/site-packages/yum/", line 210, in __init__
    max_connections = int(celem.get("maxconnections"))
TypeError: int() argument must be a string or a number, not 'NoneType'

Local variables in innermost frame:
name: 'repomd.xml'
self: <yum.metalink.MetaLinkRepoMD instance at 0x3091ab8>
elem: <Element '{}file' at 0x3095030>
filename: '/var/cache/yum/x86_64/18/fedora/metalink.xml.tmp'
repomd: <yum.metalink.MetaLinkFile instance at 0x3094098>
root: <ElementTree object at 0x3088990>
celem: <Element '{}resources' at 0x3095450>
Comment 1 Brian Morrison 2013-06-14 18:46:19 EDT
Created attachment 761454 [details]
File: backtrace
Comment 2 Brian Morrison 2013-06-14 18:46:22 EDT
Created attachment 761455 [details]
File: core_backtrace
Comment 3 Brian Morrison 2013-06-14 18:46:26 EDT
Created attachment 761456 [details]
File: environ
Comment 4 Fedora End Of Life 2013-12-21 09:01:16 EST
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2014-02-05 16:49:51 EST
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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