Bug 1296321

Summary: [SME] SSH configuration should include changing ssh_config option
Product: OpenShift Container Platform Reporter: Peter Larsen <plarsen>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: low Docs Contact:
Priority: medium    
Version: 3.1.0CC: aos-bugs, bleanhar, jokerman, mmccomas, plarsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-24 20:50:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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: