Bug 1339621

Summary:	Add or Re-Install question in Quick Installer is not Clear
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	Installer	Assignee:	Samuel Munilla <smunilla>
Status:	CLOSED ERRATA	QA Contact:	liujia <jiajliu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	abutcher, aos-bugs, bleanhar, jiajliu, jokerman, mmccomas, tdawson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: The node scaleup workflow in the quick installer has been moved out of the install subcommand and into a separate subcommand. Reason: Users reported that having the scaleup workflow inside install was confusing. Result: Scaleup now lives in it's own space and users can access it directly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 12:41:06 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 Eric Rich 2016-05-25 13:09:54 UTC

Description of problem:

Make it more clear when we say:

> By default the installer only adds new nodes to an installed environment.

> Do you want to (1) only add additional nodes or (2) reinstall the existing hosts potentially erasing any custom changes?:

In short the text here is confusing. We might want to remove this in favor of "add" or "extend" operation as a top level command with atomic-openshift-installer (install, uninstall, upgrade).

Comment 1 Eric Rich 2016-05-25 13:11:16 UTC

Should we even ask for this on a re-run of the installer? 
Wouldn't 2 always be assumed?

Comment 5 openshift-github-bot 2016-10-21 17:07:34 UTC

Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/1c7dd6d5cd94c92ebec0a0fda789f4bfffa23472
a-o-i: Separate install and scaleup workflows

In order to simplify the quick installer logic, this moves
the scaleup workflow into its own subcommand.

Fixes: Bug 1339621

Comment 7 liujia 2016-10-28 10:12:56 UTC

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

Steps:
1.check option changes
# atomic-openshift-installer --help

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

3.trigger an install with quick installer in an installed env
# atomic-openshift-installer install

Result:
1.the add nodes workflow has been splitted to s sub-command
Commands:
  install
  scaleup
  uninstall
  upgrade
2.it will install new node for scaleup the cluster successfully.

3.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.

Now re-install will fail for another issue(bug-1389701), but for this bug, i think it has been clearly splitted.

Comment 9 errata-xmlrpc 2017-01-18 12:41:06 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