Bug 1041631

Summary: 4.6 oo-install --create-config option has been removed
Product: OpenShift Container Platform Reporter: Aaron Weitekamp <aweiteka>
Component: DocumentationAssignee: Bilhar <baulakh>
Status: CLOSED DUPLICATE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.0.0CC: adellape, jokerman, libra-onpremise-devel, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-12 18:54:41 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:

Description Aaron Weitekamp 2013-12-12 18:21:53 UTC
Description of problem:
sh <(curl -s https://install.openshift.com/ose/) --create-config
Checking for necessary tools...
...looks good.
Downloading oo-install package...
Extracting oo-install to temporary directory...
Starting oo-install...
An invalid option was passed to oo-install - invalid option: --create-config
Usage: oo-install [args]

    -a, --advanced-mode              Enable access to message server and db server customization.
    -c, --config-file FILEPATH       The path to an alternate config file
    -w, --workflow WORKFLOW_ID       The installer workflow for unattended deployment.
    -e, --enterprise-mode            Show OpenShift Enterprise options (ignored in unattended mode)
    -s, --subscription-type TYPE     The software source for installation packages.
    -u, --username USERNAME          Red Hat Login username
    -p, --password PASSWORD          Red Hat Login password
    -d, --debug                      Enable debugging messages
oo-install exited; removing temporary assets.


Version-Release number of selected component (if applicable):
2.0

How reproducible:
always

Comment 1 Alex Dellapenta 2013-12-12 18:54:41 UTC

*** This bug has been marked as a duplicate of bug 1041545 ***