Bug 1296321 - [SME] SSH configuration should include changing ssh_config option
[SME] SSH configuration should include changing ssh_config option
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Scott Dodson
Xiaoli Tian
Depends On:
  Show dependency treegraph
Reported: 2016-01-06 16:44 EST by Peter Larsen
Modified: 2017-08-24 16:50 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-24 16:50:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Larsen 2016-01-06 16:44:35 EST
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.