Bug 1855751 - [OSP13->OSP16.1] Automate the addition of PermitRootLogin before running Leapp upgrade
Summary: [OSP13->OSP16.1] Automate the addition of PermitRootLogin before running Leap...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 16.1 (Train on RHEL 8.2)
Assignee: Jose Luis Franco
QA Contact: Jesse Pretorius
URL:
Whiteboard:
: 1852523 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-10 12:08 UTC by Jose Luis Franco
Modified: 2020-10-28 15:38 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-11.3.2-1.20200914170155.29a02c1.el8ost
Doc Type: Bug Fix
Doc Text:
Before this update, to successfully run a leapp upgrade during the Framework for Upgrades upgrade (FFU) from RHOSP 13 to RHOSP 16.1, the node where the Red Hat Enterprise Linux upgrade was occurring had to have the `PermitRootLogin` field defined in the ssh config file (`/etc/ssh/sshd_config`). + With this update, the Orchestration service (heat) no longer requires you to modify `/etc/ssh/sshd_config` with the `PermitRootLogin` field.
Clone Of:
Environment:
Last Closed: 2020-10-28 15:38:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 746033 0 None MERGED Add PermitRootLogin option in sshd_config before leapp. 2020-10-15 16:34:15 UTC
Red Hat Product Errata RHEA-2020:4284 0 None None None 2020-10-28 15:38:54 UTC

Description Jose Luis Franco 2020-07-10 12:08:47 UTC
Description of problem:

In order to run leapp upgrade during the FFU from OSP13 to OSP16.1 the node in which the RHEL upgrade will be performed requires to have defined the field "PermitRootLogin" into the ssh config file (/etc/ssh/sshd_config)

Right now, this is beeing addressed via documentation, by suggesting to create a playbook and run it against the overcloud nodes:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1-beta/html-single/framework_for_upgrades_13_to_16.1/index?lb_target=preview#setting-the-ssh-root-permission-parameter-on-the-overcloud-initial-steps

However, it should be fairly easy to automate such a process inside the tripleo-heat-templates so the customer doesn't need to perform extra steps.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Customer needs to run https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1-beta/html-single/framework_for_upgrades_13_to_16.1/index?lb_target=preview#setting-the-ssh-root-permission-parameter-on-the-overcloud-initial-steps to be able to leapp upgrade

Expected results:

Customer will just run the "openstack overcloud upgrade run --tags system_upgrade" command and the field will be inserted automatically before running leapp.

Additional info:

Comment 2 Jesse Pretorius 2020-08-10 15:14:28 UTC
*** Bug 1852523 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2020-10-28 15:38:25 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 bug fix and enhancement 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-2020:4284


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