Bug 1658267 - [DOC] Need to highlight the importance of setting hostname on the node before installing.
Summary: [DOC] Need to highlight the importance of setting hostname on the node before...
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-11 16:24 UTC by Ryan Howe
Modified: 2018-12-12 08:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Ryan Howe 2018-12-11 16:24:47 UTC
Document URL: 
https://docs.openshift.com/container-platform/3.11/install/host_preparation.html

Section Number and Name: 
https://docs.openshift.com/container-platform/3.11/install/host_preparation.html

Describe the issue: 

In 3.10 and + we do not allow the overwriting of openshift_hostname via the installer any longer, there are many many issues with hostnames not being correct when installing the cluster. 

We need information on how to confirm what hostname and nodename will be used before an install when installing with cloud-provider or with out cloud-provider. 

Basically we should outline that `hostname -f` will be used as the nodename and name on the server certs for the nodes and masters. We should state that this should be set to the FQDN. 

# hostnamectl set-hostname <NODE_FQDN> 

Then for cloud-provider enabled cluster we should state more clearly what hostname and nodenames will be used, and state that best practice is to make sure `hostname -f` also gets set to this to avoid confusion. 


Additional information: 
KCS with some details: 
https://access.redhat.com/solutions/3738701


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