Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1339621 - Add or Re-Install question in Quick Installer is not Clear
Add or Re-Install question in Quick Installer is not Clear
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.2.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Samuel Munilla
liujia
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-05-25 09:09 EDT by Eric Rich
Modified: 2017-03-08 13 EST (History)
7 users (show)

See Also:
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 07:41:06 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Eric Rich 2016-05-25 09:09:54 EDT 
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 09:11:16 EDT 
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 13:07:34 EDT 
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 06:12:56 EDT 
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 07:41:06 EST 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.