Bug 1623159 - Live Migration over SSH Failing due to target on non-default port
Summary: Live Migration over SSH Failing due to target on non-default port
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Ollie Walsh
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On:
Blocks: 1600184
TreeView+ depends on / blocked
 
Reported: 2018-08-28 15:26 UTC by awaugama
Modified: 2023-02-22 23:02 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180831204458.17bb71e.0rc1.0rc1.el7ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:51:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1789452 0 None None None 2018-08-28 15:26:02 UTC
OpenStack gerrit 597165 0 'None' MERGED Include ssh known_hosts entries for non-default port 2020-08-14 01:09:35 UTC
OpenStack gerrit 598137 0 'None' MERGED Simplify ssh known_hosts entries for non-default port 2020-08-14 01:09:35 UTC
OpenStack gerrit 601817 0 'None' MERGED Include ssh known_hosts entries for non-default port 2020-08-14 01:09:35 UTC
OpenStack gerrit 601818 0 'None' MERGED Simplify ssh known_hosts entries for non-default port 2020-08-14 01:09:35 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:52:58 UTC

Description awaugama 2018-08-28 15:26:02 UTC
Description of problem: When a target compute node isn't using the default port, ssh requires a known_hosts entry that isn't present with the latest tripleo deployment of OpenStack


Version-Release number of selected component (if applicable):

openstack-tripleo-common.noarch  9.2.1-0.20180803214330.el7ost


How reproducible: Everytime


Steps to Reproduce:
1. Create an instance with shared storage
2. Attempt to live migrate the instance

Actual results:

The instance live migrates to the other compute node

Expected results:

Live migration fails

Additional info: 
From the upstream bug:

It appears the behaviour of ssh client has changed. Previously a port was not required in /etc/ssh/ssh_known_hosts when running on a non-default port, now it is:

[root@compute-1 heat-admin]# ssh compute-0.localdomain
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

[root@compute-1 heat-admin]# ssh -p 2022 compute-0.localdomain
The authenticity of host '[compute-0.localdomain]:2022 ([172.17.1.19]:2022)' can't be established.
ECDSA key fingerprint is SHA256:1kTWyAQTD3K1vGsiQQitfRChSk1drrtewcZ82VhGx1c.
ECDSA key fingerprint is MD5:61:53:4a:e2:69:a6:b9:8b:70:39:8f:a6:a2:20:18:bd.
Are you sure you want to continue connecting (yes/no)? ^C

Comment 8 Joe H. Rahme 2018-10-03 12:26:20 UTC
Live migration works out of the box as of puddle 2018.09.27.1

Comment 16 errata-xmlrpc 2019-01-11 11:51:31 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, 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/RHEA-2019:0045


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