Bug 996453
Summary: | yum crashes with 'TypeError: 'NoneType' object is not callable' when packages are not downloadable | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Frantisek Reznicek <freznice> |
Component: | rhn-client-tools | Assignee: | Milan Zázrivec <mzazrivec> |
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.10 | CC: | esammons, freznice, james.antill, lmiksik, lzhaldyb, mkudlej, sgraf, zpavlas |
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: | 2013-12-17 11:41:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1049888 |
Description
Frantisek Reznicek
2013-08-13 08:08:11 UTC
I believe the root problem is in rhnplugin, but re-raising the exception in exFatal hides it. I had no luck reproducting it yet. I still don't know how it causes the "NoneType is not callable" error, but a likely candidate is errorneous "raise None" at rhnplugin.py:493 .. however, it might be something else, too. --- a/yummain.py +++ b/yummain.py @@ -64,6 +64,7 @@ def main(args): return 1 def exFatal(e): + raise logger.critical('\n\n%s', exception2msg(e.value)) if unlock(): return 200 return 1 Could you add this 1-liner to yummain.py, and trigger the bug again? It should print a more meaningful traceback then, and we can then fix the problem at the origin. I'm sorry unable to re-trigger the issue again as it was caused under special (bad) networking case. Finally found the root cause.. Indeed, it was rhnplugin raising an instance of an invalid YumBaseError subclass. When I fix BZ 751294 with adding "raise AttributeError, name" at the end of up2dateErrors.Error.__getattr__(), I no longer get the traceback, but a "Network Error" message. Maybe this should be closed as a dupe. I'm not quite sure what should I do with this bug report at this point. Is there anything that is to be fixed in yum-rhn-plugin? I'd close this as a dupe of BZ 751294 since the cause is the same. *** This bug has been marked as a duplicate of bug 751294 *** |