Bug 460871 - multiple same messages when loading yum with versionlock plugin
multiple same messages when loading yum with versionlock plugin
Status: CLOSED INSUFFICIENT_DATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum-utils (Show other bugs)
5.3
All Linux
medium Severity medium
: rc
: ---
Assigned To: James Antill
James Antill
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-02 04:34 EDT by Jan Hutař
Modified: 2013-03-12 16:20 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-12 16:20:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
"RuntimeError: maximum recursion depth exceeded" when no repos configured (127.95 KB, text/plain)
2008-09-02 04:34 EDT, Jan Hutař
no flags Details

  None (edit)
Description Jan Hutař 2008-09-02 04:34:10 EDT
Created attachment 315506 [details]
"RuntimeError: maximum recursion depth exceeded" when no repos configured

Description of problem:
When I have yum-versionlock plugin enabled, I get "Reading version lock configuration" message 3 times.


Version-Release number of selected component (if applicable):
yum-3.2.19-6.el5.noarch
yum-versionlock-1.1.16-4.el5.noarch


How reproducible:
always


Steps to Reproduce:
1. disable all plugins except of versionlock one
2. # yum upgrade


Actual results:
# yum upgrade
Loaded plugins: versionlock
Reading version lock configuration
Setting up Upgrade Process
Reading version lock configuration
Reading version lock configuration
No Packages marked for Update


Expected results:
# yum upgrade
Loaded plugins: versionlock
Reading version lock configuration
Setting up Upgrade Process
No Packages marked for Update


Additional info:
When there is something to update, I get that message only once:

# yum upgrade --enablerepo=53_div_10 yum
Loaded plugins: versionlock
Reading version lock configuration
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package yum.noarch 0:3.2.19-6.el5 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package      Arch            Version               Repository            Size 
================================================================================
Updating:
 yum          noarch          3.2.19-6.el5          53_div_10             923 k

Transaction Summary
================================================================================
Install      0 Package(s)         
Update       1 Package(s)         
Remove       0 Package(s)         

Total download size: 923 k
Is this ok [y/N]: y
Downloading Packages:
yum-3.2.19-6.el5.noarch.rpm                                            | 923 kB     00:02     
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating       : yum                                               [1/2] 
  Cleanup        : yum                                               [2/2] 

Updated: yum.noarch 0:3.2.19-6.el5
Complete!



Yesterday I got this (I can't reproduce it now, maybe some bad metadata - I made `rm -rf /var/cache/yum/*` - sorry :-() - full log attached:

# yum repolist
Loaded plugins: versionlock
repolist: 0
# yum upgrade &> /tmp/no-repos-maximum-recursion.log   # (attached)
Loaded plugins: versionlock
Reading version lock configuration
Reading version lock configuration
Reading version lock configuration
...
  File "/usr/lib/yum-plugins/versionlock.py", line 66, in exclude_hook
    for pkg in vl_search(conduit, pkgname):
  File "/usr/lib/yum-plugins/versionlock.py", line 31, in vl_search
    return conduit._base.pkgSack.searchNevra(name=name)
  File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 591, in <lambda>
    pkgSack = property(fget=lambda self: self._getSacks(),
  File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 446, in _getSacks
    self.plugins.run('exclude')
  File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 176, in run
    func(conduitcls(self, self.base, conf, **kwargs))
  File "/usr/lib/yum-plugins/versionlock.py", line 40, in exclude_hook
    llfile = urlgrabber.urlopen(location)
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 611, in urlopen
    return default_grabber.urlopen(url, **kwargs)
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 890, in urlopen
    return self._retry(opts, retryfunc, url)
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 851, in _retry
    r = apply(func, (opts,) + args, {})
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 889, in retryfunc
    return URLGrabberFileObject(url, filename=None, opts=opts)
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 1007, in __init__
    self._do_open()
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 1090, in _do_open
    fo, hdr = self._make_request(req, opener)
  File "/usr/lib/python2.4/site-packages/urlgrabber/grabber.py", line 1203, in _make_request
    fo = opener.open(req)
  File "/usr/lib/python2.4/urllib2.py", line 358, in open
    response = self._open(req, data)
  File "/usr/lib/python2.4/urllib2.py", line 376, in _open
    '_open', req)
  File "/usr/lib/python2.4/urllib2.py", line 337, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.4/urllib2.py", line 1116, in file_open
    return self.open_local_file(req)
  File "/usr/lib/python2.4/urllib2.py", line 1136, in open_local_file
    headers = mimetools.Message(StringIO(
  File "/usr/lib/python2.4/mimetools.py", line 16, in __init__
    rfc822.Message.__init__(self, fp, seekable)
  File "/usr/lib/python2.4/rfc822.py", line 106, in __init__
    self.readheaders()
  File "/usr/lib/python2.4/rfc822.py", line 168, in readheaders
    elif self.iscomment(line):
RuntimeError: maximum recursion depth exceeded

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