Log traceback for initialize connection failure

Currently the manager logs at 'error' level when driver
initialize_connection fails before throwing VolumeBackendAPIException.
The original traceback will not be logged and this would make debugging
difficult. This patch changes the log level to 'exception' to log the
traceback before raising the exception.

Change-Id: I0e981120dee165a341c9015f62738e3b375afb00
Closes-bug: #1599052
This commit is contained in:
Vipin Balachandran 2016-07-05 12:49:59 +05:30
parent 4415c6fcb5
commit 00bce241e8
1 changed files with 1 additions and 1 deletions

View File

@ -1363,7 +1363,7 @@ class VolumeManager(manager.SchedulerDependentManager):
except Exception as err:
err_msg = (_("Driver initialize connection failed "
"(error: %(err)s).") % {'err': six.text_type(err)})
LOG.error(err_msg, resource=volume)
LOG.exception(err_msg, resource=volume)
self.driver.remove_export(context.elevated(), volume)