Closed
Bug 1040397
Opened 10 years ago
Closed 6 years ago
"KeyError during shutdown" has returned
Categories
(Cloud Services Graveyard :: Server: Token, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rfkelly, Unassigned)
Details
(Whiteboard: [qa+])
Per Bug 1040396 Comment 6: """ Related to that: /media/ephemeral0/logs/tokenserver/token.error.log Exception KeyError: KeyError(22260464,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored So, the Key Error shows up in the hekad logs and the token error logs... """ This is a janky python thing caused by some bad module shutdown ordering. I thought we had a fix in place for it but it seems to be back. Not a high priority but it would be good not to crowd the logs.
Updated•10 years ago
|
Whiteboard: [qa+]
Reporter | ||
Comment 1•10 years ago
|
||
Apparently this is a known bad interaction with gevent, caused by incorrect import order: http://stackoverflow.com/questions/8774958/keyerror-in-module-threading-after-a-successful-py-test-run We should put some hooks in place to detect it and error out early rather than getting into this state that gives errors on shutdown.
Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•