Bug 1278243 - Confusing prompt from atomic-openshift-installer
Summary: Confusing prompt from atomic-openshift-installer
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 03:48 UTC by Gaoyun Pei
Modified: 2015-11-20 15:41 UTC (History)
4 users (show)

Fixed In Version: atomic-openshift-utils-3.0.7-1.git.76.c73ec7b.el7aos.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-20 15:41:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gaoyun Pei 2015-11-05 03:48:09 UTC
Description of problem:
When running "atomic-openshift-installer install" with existing env, it would inform user the env is already installed and saying:
"If you want a fresh install, use --force "
But no such option could be used and no such option in help page.

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.7-1.git.48.75d357c.el7aos.noarch

How reproducible:
Always

Steps to Reproduce:
1.[root@openshift-v3 ~]# atomic-openshift-installer --unattended install
Gathering information from hosts...
10.x.x.111 is already an OpenShift Master
10.x.x.122 is already an OpenShift Node
Installed environment detected and no additional nodes specified: aborting. If you want a fresh install, use --force

2.[root@openshift-v3 ~]# atomic-openshift-installer  --unattended --force install
Error: no such option: --force

3. [root@openshift-v3 ~]# atomic-openshift-installer --help
Usage: atomic-openshift-installer [OPTIONS] COMMAND [ARGS]...

  The main click CLI module. Responsible for handling most common CLI
  options, assigning any defaults and adding to the context for the sub-
  commands.

Options:
  -u, --unattended
  -c, --configuration PATH
  -a, --ansible-playbook-directory DIRECTORY
  --ansible-config PATH
  --ansible-log-path PATH
  --help                          Show this message and exit.

Commands:
  install
  uninstall
  upgrade


Actual results:


Expected results:


Additional info:

Comment 1 Brenton Leanhardt 2015-11-05 21:34:49 UTC
This will be fixed in the next puddle.  The output will now report:

If you want a fresh install, use `atomic-openshift-installer install --force`

I've heard a limitation of the cli library we use keeps us from being able to run 'atomic-openshift-installer  --unattended --force install'.

Comment 3 Gaoyun Pei 2015-11-06 05:25:11 UTC
Verify this bug with openshift-ansible-3.0.7-1.git.76.c73ec7b.el7aos.noarch.

When running with config file and all installed hosts in the file using 'atomic-openshift-installer -u install', it would prompt: 

Installed environment detected and no additional nodes specified: aborting. If you want a fresh install, use `atomic-openshift-installer install --force`

Use --force to reinstall the installed env
[root@openshift-v3 ~]# atomic-openshift-installer -c installer.cfg.yml -u install --force
Gathering information from hosts...
Installed environment detected.
192.168.1.233 is already an OpenShift Master
192.168.1.234 is already an OpenShift Node
Writing config to: installer.cfg.yml
Ready to run installation process.

PLAY [Populate config host groups] ******************************************** 

TASK: [fail ] ***************************************************************** 
skipping: [localhost]
...


Note You need to log in before you can comment on or make changes to this bug.