Bug 1267486

Summary:	Installation documentation - mark master as unschedulable node not possible at this stage.
Product:	OKD	Reporter:	Trond Magnussen <trond>
Component:	Documentation	Assignee:	Alex Dellapenta <adellape>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Bilhar <baulakh>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	3.x	CC:	adellape, aos-bugs, mmccomas
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:	2016-05-16 14:33:39 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 Trond Magnussen 2015-09-30 07:34:17 UTC

Description of problem:
https://docs.openshift.org/latest/install_config/install/advanced_install.html#configuring-ansible

“Before running the Ansible installer, any hosts you intend to designate as masters during the installation process should also be configured as unschedulable nodes, in order to configure the masters as part of the OpenShift SDN.”

Comment: I think this is not needed, as the link “unschedulable” goes to this page https://docs.openshift.org/latest/admin_guide/manage_nodes.html#marking-nodes-as-unschedulable-or-schedulable which describe to use “oadm” command.   
This command is not found at this stage of the installation, and I have heard that the Ansible installation make node “unschedulable” as long as it is marked as “master” and not “node” in /etc/ansible/hosts    Is that correct ? 


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


How reproducible:
Install Openshift exactly as the documentation describes ... :) 
(OS: CentOS 7.1)

Steps to Reproduce:
1.
2.
3.

Actual results:
oadm  : command not found

Expected results:
I think this step is not needed. 

Additional info:

Comment 2 Alex Dellapenta 2015-10-16 19:16:07 UTC

The way it's worded, it makes it sound like it's a task you need to perform, however the installation process takes care of it for you. It's still worth noting what is taking place, but it should be reworded to make things more clear.

Comment 4 Alex Dellapenta 2015-10-16 19:22:56 UTC

Duplicate GH Issue here: https://github.com/openshift/openshift-docs/issues/1017

Comment 6 Alex Dellapenta 2016-05-16 14:33:39 UTC

The Quick Installation topic now has the following Note admonition to explain what automatically happens for masters:

https://docs.openshift.com/enterprise/latest/install_config/install/quick_install.html#quick-before-you-begin

"By default, any hosts you designate as masters during the installation process are automatically also configured as nodes so that the masters are configured as part of the OpenShift SDN. The node component on the masters, however, are marked unscheduable, which blocks pods from being scheduled on it. After the installation, you can mark them schedulable if you want."

And the Advanced Installation topic now has the following subsection under "Configuring Ansible" to make it more clear how you can control this at installation time:

https://docs.openshift.com/enterprise/latest/install_config/install/advanced_install.html#marking-masters-as-unschedulable-nodes