zaqar/zaqar
Sean McGinnis e135e43935
Fix exception mishandling
There were a lot of instances of exceptions being raised or logged
incorrectly.

When reraising an exception, "raise" should be called, not "raise ex".
The second form will cause the original traceback to be modified to the
new location.

LOG.exception is the same as LOG.error with the additional behavior of
logging any exception that is in the current scope. Therefore, doing
something like "LOG.exception(ex)" is redundant and causes the exception
message to be logged twice. Logging should be done with some sort of
textual message without the exception object.

Change-Id: I149c8fe7ef4b6628f910943587ab4302cc371441
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-05-29 17:12:31 -05:00
..
api Fix exception mishandling 2019-05-29 17:12:31 -05:00
bench Update os_client_config to openstack.config 2018-07-27 08:46:11 +08:00
cmd Add zaqar-status upgrade check command framework 2018-12-12 06:08:06 +00:00
common Fix exception mishandling 2019-05-29 17:12:31 -05:00
conf Introduce the Topic resource into Zaqar-1 2019-03-07 10:16:39 +08:00
hacking Add log hacking rules 2017-07-05 03:12:32 -04:00
locale Imported Translations from Zanata 2019-02-01 08:08:28 +00:00
notification Using smtplib for Zaqar mail delivery 2018-08-21 01:06:07 +00:00
storage Fix exception mishandling 2019-05-29 17:12:31 -05:00
tests Unblock gate failures 2019-05-29 09:31:18 -05:00
transport Fix exception mishandling 2019-05-29 17:12:31 -05:00
__init__.py Refactor code structure for notification 2014-12-09 16:19:42 +13:00
bootstrap.py Fix exception mishandling 2019-05-29 17:12:31 -05:00
context.py Remove deprecated context usage 2017-09-22 01:17:51 +00:00
i18n.py Update and optimize documentation links 2017-07-20 18:31:18 +08:00
version.py Introduce Guru to Zaqar 2017-03-09 11:00:29 +08:00