Add test caller to scenario manager ssh connection failure for tracking
test_volume_boot_pattern (v1 and v2) has been failing with generic
SSHTimeout for awhile now but due to the very generic nature of the
failure we don't have a fingerprint in elastic-recheck for tracking the
problem.
This adds the specific error to the message that's logged and adds the
test caller so we can track specific tests hitting this failure rather
than everything that could possibly hit it and muddle the bug
categorization in elastic-recheck.
Related-Bug: #1355573
Change-Id: I7b37af339aea1be0cbe4bae1156e9f5dc20d0dd7
diff --git a/tempest/scenario/manager.py b/tempest/scenario/manager.py
index 50aa261..cfd5169 100644
--- a/tempest/scenario/manager.py
+++ b/tempest/scenario/manager.py
@@ -20,6 +20,7 @@
from oslo_log import log
import six
from tempest_lib.common.utils import data_utils
+from tempest_lib.common.utils import misc as misc_utils
from tempest_lib import exceptions as lib_exc
from tempest.common import fixed_network
@@ -307,8 +308,13 @@
password=password)
try:
linux_client.validate_authentication()
- except Exception:
- LOG.exception('Initializing SSH connection to %s failed' % ip)
+ except Exception as e:
+ message = ('Initializing SSH connection to %(ip)s failed. '
+ 'Error: %(error)s' % {'ip': ip, 'error': e})
+ caller = misc_utils.find_test_caller()
+ if caller:
+ message = '(%s) %s' % (caller, message)
+ LOG.exception(message)
# If we don't explicitly set for which servers we want to
# log the console output then all the servers will be logged.
# See the definition of _log_console_output()