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).
Should we even ask for this on a re-run of the installer? Wouldn't 2 always be assumed?
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
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.
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