Bug 1487034 - OSP11 -> OSP12: live migration fails, different ssh port is used
Summary: OSP11 -> OSP12: live migration fails, different ssh port is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 12.0 (Pike)
Assignee: Emilien Macchi
QA Contact: Marius Cornea
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-31 06:12 UTC by Ollie Walsh
Modified: 2018-02-05 19:12 UTC (History)
13 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost puppet-tripleo-7.4.3-0.20171019174214.1e9000a.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 21:59:22 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 505590 0 None MERGED Support for Ocata-Pike live-migration over ssh 2020-08-14 01:16:18 UTC
OpenStack gerrit 506957 0 None MERGED Support for Ocata-Pike live-migration over ssh 2020-08-14 01:16:18 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Ollie Walsh 2017-08-31 06:12:13 UTC 
Description of problem:

On baremetal compute nodes live migration over ssh uses the default port 22. When computes are containerized a second ssh daemon is run (via docker) on port 2022 (by default) while baremetal sshd service continues running on the baremetal host for admin.

As the port is encoded in the live_migration_uri in nova.conf it is not possible to live migration from baremetal to containerized and vice-versa.
Comment 10 errata-xmlrpc 2017-12-13 21:59:22 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-2017:3462
Note You need to log in before you can comment on or make changes to this bug.