exception tracebacks are lost when using raise
Bug #845866 reported by
Vish Ishaya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Russell Bryant | ||
oslo-incubator |
Fix Released
|
Low
|
Russell Bryant | ||
Grizzly |
Fix Released
|
Low
|
Russell Bryant |
Bug Description
Since switching the db code to use an eventlet library, we can no longer re-raise exceptions if there is any db access in the exception handler. There are a number of places in the code where this is done.
we need to change instances of
except <SomeException>:
# code that uses db or rpc
raise
to:
except <SomeException>:
with excutils.
# code that uses db or rpc
Also adding a logging.
Changed in nova: | |
importance: | Undecided → Low |
milestone: | none → 2011.3 |
status: | New → Triaged |
Changed in nova: | |
milestone: | 2011.3 → none |
Changed in nova: | |
milestone: | none → grizzly-rc1 |
tags: | added: low-hanging-fruit |
description: | updated |
Changed in nova: | |
assignee: | nobody → Russell Bryant (russellb) |
Changed in oslo: | |
assignee: | nobody → Russell Bryant (russellb) |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in oslo: | |
milestone: | none → grizzly-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Arg, this is unfortunate. This whole eventlet + SQLAlchemy thing has been a pain...but I'm not sure how the rest of the world deals with it. Maybe I'll make a summit brainstorming session over this because it's been the source of a number of bugs.