Bug 1368003

Summary:	add node/reinstall against ose-3.3 fail when quick install with an config file which has new node and installed node
Product:	OpenShift Container Platform	Reporter:	liujia <jiajliu>
Component:	Installer	Assignee:	Samuel Munilla <smunilla>
Status:	CLOSED ERRATA	QA Contact:	liujia <jiajliu>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	aos-bugs, bleanhar, jdetiber, jokerman, mmccomas, tdawson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 12:52:28 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:

Comment 2 liujia 2016-08-18 07:57:04 UTC

the same problem:
when run "atomic-openshift-installer -u install", it will directly abort auto with msg but not output the choice items which should be given as a hint.

Comment 3 Samuel Munilla 2016-10-24 15:15:43 UTC

https://github.com/openshift/openshift-ansible/pull/2563

Comment 5 liujia 2016-10-28 10:17:43 UTC

Version:
atomic-openshift-utils-3.4.13-1.git.0.ff1d588.el7.noarch

Steps:
1.trigger an install with quick installer in an installed env
# atomic-openshift-installer install

2.trigger an scaleup with quick installer in an installed env
# atomic-openshift-installer scaleup

Result:
1.it will hint user for an mixed env and warn user to continue for reinstall:
input(n), it will exit.
input(y), it will go to reinstall workflow and run install playbook again for the cluster.

2.it will install new node for scaleup the cluster successfully.

Now add new node and re-install have been splitted and it can go to corresponding workflow successfully, but for specified installer.cfg.yml, it still has another issue which has been tracked in another bug-Bug 1389667. As for this bug, i think it is fixed.

Comment 7 errata-xmlrpc 2017-01-18 12:52:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0066