Bug 1294088

Summary:	[DOCS] Failed install warning for Multiple Masters
Product:	OpenShift Container Platform	Reporter:	Ryan Howe <rhowe>
Component:	Documentation	Assignee:	brice <bfallonf>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jianwei Hou <jhou>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	3.1.0	CC:	aos-bugs, jokerman, 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:	2017-12-30 22:40:35 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 Ryan Howe 2015-12-24 15:20:00 UTC

Document URL: https://docs.openshift.com/enterprise/3.1/install_config/install/advanced_install.html#installer-known-issues

Section Number and Name:  Failed install on HA environment 

Describe the issue:

Multiple Masters
**"On failure of the Ansible installer, you must start from a clean operating system installation. If you are using virtual machines, start from a fresh image."** 

- The warning here is very concerning when deploying a HA environment. Once the environment is up and running in order to add additional masters or etcd hosts the installer must be run again. This warning suggests that if the install fails the whole production environment is jeopardized. 


Suggestions for improvement: 

- Add information on what is needed to add additional masters and etcd hosts.  
- Add trouble shooting steps if install failed
- Add information on what the ansible installer changes when rerun 
- Add information on what is changed when adding another master, ectd, or node. 
- Clarify that this warning is only on fresh installs (if that is the case) 



Additional information:

Comment 1 Vikram Goyal 2017-12-30 22:40:35 UTC

Looks like information was updated to include HA environments.

I am closing this bug, but please feel free to reopen if the added information is not enough.