yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02021
[Bug 845866] Re: exception tracebacks are lost when using raise
** Changed in: oslo/grizzly
Importance: Undecided => Low
** Changed in: oslo/grizzly
Status: New => Fix Released
** Changed in: oslo/grizzly
Milestone: None => 2013.1
** Changed in: oslo/grizzly
Assignee: (unassigned) => Russell Bryant (russellb)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/845866
Title:
exception tracebacks are lost when using raise
Status in OpenStack Compute (Nova):
Fix Released
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Status in oslo grizzly series:
Fix Released
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.save_and_reraise_exception():
# code that uses db or rpc
Also adding a logging.exception('useful message') is probably a good
idea in most cases if the original traceback is important.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/845866/+subscriptions