Bug 1897139 - If paramiko SSH client connection fails because of authentication, cannot reconnect
Summary: If paramiko SSH client connection fails because of authentication, cannot rec...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-neutron-tests-tempest
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Slawek Kaplonski
QA Contact: Candido Campos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-12 12:19 UTC by Slawek Kaplonski
Modified: 2021-03-17 15:36 UTC (History)
2 users (show)

Fixed In Version: python-neutron-tests-tempest-0.9.0-1.20201113201944.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-17 15:35:39 UTC
Target Upstream Version:
Embargoed:
skaplons: needinfo-
skaplons: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1892861 0 None None None 2020-11-12 12:19:25 UTC
OpenStack gerrit 758968 0 None MERGED Check VM's console log before trying to SSH to it. 2021-02-17 07:01:23 UTC
Red Hat Product Errata RHBA-2021:0817 0 None None None 2021-03-17 15:36:03 UTC

Description Slawek Kaplonski 2020-11-12 12:19:26 UTC
In the VM boot process, cloud-init copies the SSH keys.

If the tempest test tries to connect to the VM before the SSH keys are copied, the SSH client will raise a paramiko.ssh_exception.AuthenticationException. From this point, even when the SSH keys are copied into the VM, the SSH client cannot reconnect anymore into the VM using the pkey.

If a bigger sleep time is added manually (to avoid this race condition: try to connect when the IP is available in the port but the SSH keys are still not present in the VM), the SSH client connects without any problem.

[1]http://paste.openstack.org/show/797127/

Comment 17 errata-xmlrpc 2021-03-17 15:35:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.1.4 director bug fix advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:0817


Note You need to log in before you can comment on or make changes to this bug.