After doing some debugging, this bug appears in trunk dynamic workloads when ssh to jumphost is required. This bug seems to appear because of the behaviour of the paramiko module when installed inside a venv. I tried calling client.connect(<host_ip>, username=<username>, pkey=<private key>) both inside rally venv and outside rally venv. Inside rally venv, ssh fails multiple times with message
"Ssh is still unavailable: SSHError("Exception <class 'paramiko.ssh_exception.Au
thenticationException'> was raised during connect to cirros@172.31.9.177:22. Exception value is: AuthenticationException('Authentication failed.',
)",)",
and finally the cirros host stops accepting ssh connections, causing the error in the original issue.
When the same function call is made after deactivating rally venv, it works on the first attempt.
A stackoverflow[1] answer explains this issue.
After doing some debugging, this bug appears in trunk dynamic workloads when ssh to jumphost is required. This bug seems to appear because of the behaviour of the paramiko module when installed inside a venv. I tried calling client. connect( <host_ip> , username= <username> , pkey=<private key>) both inside rally venv and outside rally venv. Inside rally venv, ssh fails multiple times with message ssh_exception. Au eption' > was raised during connect to cirros@ 172.31. 9.177:22. Exception value is: AuthenticationE xception( 'Authentication failed.',
"Ssh is still unavailable: SSHError("Exception <class 'paramiko.
thenticationExc
)",)",
and finally the cirros host stops accepting ssh connections, causing the error in the original issue.
When the same function call is made after deactivating rally venv, it works on the first attempt.
A stackoverflow[1] answer explains this issue.
[1] https:/ /stackoverflow. com/a/70794909