From 81066a05df3a4a9ba8c372a910af38768520a1b5 Mon Sep 17 00:00:00 2001 From: Eric Harney Date: Fri, 1 Jul 2016 10:55:42 -0400 Subject: [PATCH] Log terminate_connection exception with traceback The volume manager is not logging a traceback for volume driver terminate_connection failures. This can result in an opaque error message which is hard to troubleshoot. Closes-Bug: #1598214 Change-Id: Ibde64e0715cc861b73434e6a9c676c7e25a37a18 --- cinder/volume/manager.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cinder/volume/manager.py b/cinder/volume/manager.py index a23c522b4e1..0454175b819 100644 --- a/cinder/volume/manager.py +++ b/cinder/volume/manager.py @@ -1428,7 +1428,7 @@ class VolumeManager(manager.SchedulerDependentManager): except Exception as err: err_msg = (_('Terminate volume connection failed: %(err)s') % {'err': six.text_type(err)}) - LOG.error(err_msg, resource=volume_ref) + LOG.exception(err_msg, resource=volume_ref) raise exception.VolumeBackendAPIException(data=err_msg) LOG.info(_LI("Terminate volume connection completed successfully."), resource=volume_ref)