Bug 1296321 - [SME] SSH configuration should include changing ssh_config option
Summary: [SME] SSH configuration should include changing ssh_config option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-06 21:44 UTC by Peter Larsen
Modified: 2017-08-24 20:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-24 20:50:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter Larsen 2016-01-06 21:44:35 UTC
Document URL: https://docs.openshift.com/enterprise/3.1/install_config/install/prerequisites.html#ensuring-host-access

Section Number and Name: https://docs.openshift.com/enterprise/3.1/install_config/install/prerequisites.html#ensuring-host-access

Describe the issue: 
The SSH setup should include turning off the strict hostname checking, to avoid the installer from stopping and prompting for short/long hostnames to be entered into the knownhosts file. 

When a customer installs, if they use short names to do ssh with, when the installer uses the FQDN it will stop and prompt for all the hosts. This can be avoided by either changing the install script to specify "no' for StrickHostChecking, or by changing the setting in /etc/ssh/ssh_config on the installation host.

Suggestions for improvement:

Add the following command to the instructions:

cat "     StrictHostKeyChecking no" >> /etc/ssh/ssh_config

Alternatively, the install script (ansible) could use 

ssh -o "StrictHostKeyChecking no" every time it does an ssh call.

Additional information:


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