This is a very old bug. Anna set it back to new in Aug 2016 as it may be 
related to, which has been fixed 
Hence I will set this to invalid. If some hits an ssh bug in the gate again, 
please file a new bug.

** Changed in: tempest
       Status: New => Invalid

** Changed in: tempest
   Importance: Critical => Undecided

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  SSHTimeout in tempest trying to verify that computes are actually

Status in Cinder:
Status in OpenStack Compute (nova):
  Fix Released
Status in tempest:

Bug description:
  failed at least once with the following traceback when trying to
  connect via SSH:

  Traceback (most recent call last):
    File "tempest/scenario/", line 156, in 
      ssh_client = self._ssh_to_server(instance_from_snapshot, keypair)
    File "tempest/scenario/", line 100, in 
    File "tempest/scenario/", line 466, in get_remote_client
      return RemoteClient(ip, username, pkey=private_key)
    File "tempest/common/utils/linux/", line 47, in __init__
      if not self.ssh_client.test_connection_auth():
    File "tempest/common/", line 149, in test_connection_auth
      connection = self._get_ssh_connection()
    File "tempest/common/", line 65, in _get_ssh_connection
      timeout=self.channel_timeout, pkey=self.pkey)
    File "/usr/local/lib/python2.7/dist-packages/paramiko/", line 236, 
in connect
      retry_on_signal(lambda: sock.connect(addr))
    File "/usr/local/lib/python2.7/dist-packages/paramiko/", line 279, 
in retry_on_signal
      return function()
    File "/usr/local/lib/python2.7/dist-packages/paramiko/", line 236, 
in <lambda>
      retry_on_signal(lambda: sock.connect(addr))
    File "/usr/lib/python2.7/", line 224, in meth
      return getattr(self._sock,name)(*args)
"/usr/local/lib/python2.7/dist-packages/fixtures/_fixtures/", line 
52, in signal_handler
      raise TimeoutException()

  Logs can be found at:
  The review that triggered the issue is:

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to