Red Hat Bugzilla – Bug 548500
[abrt] crash detected in yum-utils-1.1.24-2.fc13
Last modified: 2014-01-21 18:12:57 EST
abrt 1.0.0 detected a crash.
Summary: TB69b28093 yumRepo.py:1444:_getRepoXML:RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
Traceback (most recent call last):
File "/usr/bin/repo-graph", line 118, in <module>
File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 84, in doTsSetup
File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 99, in _getTs
File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 110, in _getTsInfo
pkgSack = self.pkgSack
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 724, in <lambda>
pkgSack = property(fget=lambda self: self._getSacks(),
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 553, in _getSacks
File "/usr/lib/python2.6/site-packages/yum/repos.py", line 277, in populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 164, in populate
if self._check_db_version(repo, mydbtype):
File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 223, in _check_db_version
File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1258, in _check_db_version
repoXML = self.repoXML
File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1448, in <lambda>
repoXML = property(fget=lambda self: self._getRepoXML(),
File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1444, in _getRepoXML
raise Errors.RepoError, msg
RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
Local variables in innermost frame:
msg: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
e: Cannot retrieve metalink for repository: fedora. Please verify its path and try again
cmdline: /usr/bin/python /usr/bin/repo-graph
Created attachment 379037 [details]
Can you post your /etc/yum.repos.d/fedora.repo file. Thanks
Created attachment 379059 [details]
if you run:
yum repolist -v
does that work?
No. Here's the output.
[draco@alanine ~]$ yum repolist -v
Not loading "blacklist" plugin, as it is disabled
Loading "dellsysidplugin2" plugin
Loading "fastestmirror" plugin
Loading "presto" plugin
Loading "refresh-packagekit" plugin
Not loading "whiteout" plugin, as it is disabled
Config time: 0.204
rpmdb time: 0.076
Yum Version: 3.2.25
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=x86_64&country=EU error was
14: PYCURL ERROR 7 - ""
http://download.fedoraproject.org/pub/fedora/linux/development/x86_64/os/repodata/repomd.xml: [Errno 14] PYCURL ERROR 7 - ""
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rawhide. Please verify its path and try again
I think you're seeing:
*** This bug has been marked as a duplicate of bug 548269 ***
I've also applied a patch upstream so this won't traceback in the future.
Wait, this can't be duplicate of 548269. The bug report is about a *crash* detected in yum-utils. Bug 548269 is *not* about any crash. Situation that any mirror is not available may happen independently on curl. I don't think it is enough reason to crash. The crash itself simply can't be fixed in curl.
You'll note the crash is 'cannot find metalink'. Here's how the crash would occur:
repo-graph attempts to grab info from the repos.
it cannot reach the repo b/c of the issue in 548269
it raises a repoerror
this crashed repo-graph b/c it is not expecting the exception.
1. this is started by the issue in 548269
2. I applied an exception catch in repo-graph to handle these problems in the future.
Does "exception catch" mean yum-util won't crash next time it happens?
If so, the bug itself (crash) has been resolved within yum-utils. Closing it as duplicate can cause only confusion. As duplicates are usually marked bugs with the same behavior and the same resolution.
It means the exception has been caught. The CAUSE of the exception is why I closed it as a duplicate.
Why is this such a big deal?
It would be also good to attach and/or reference the patch you applied upstream and mention the version in which the flaw was fixed.
> Why is this such a big deal?
Because duplicated bugs are handled differently when searching on BZ. People may need to know this bug has been already reported and fixed.
Have you looked at what repograph does? Have you looked at how seldom it is used by anyone? I almost removed it from yum-utils b/c it is completely frelling silly.
Here's the exciting patch:
closed upstream - hope you're completely happy.
(In reply to comment #14)
> It's REPOGRAPH!
It may sounds stupid but I have really no idea what repograph is :-)
You seems to be more educated about repograph, so you can summarize it briefly. Other people encountering the bug may be also interested. The title is "[abrt] crash detected in yum-utils...", so I started from there. If it is misleading, you may tweak the title as well.
Thanks for the link!
yum-utils-1.1.25-1.fc12 has been submitted as an update for Fedora 12.
yum-utils-1.1.25-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.