Bug 1271035 - The '-t' parameter doesn't work for oo-install
Summary: The '-t' parameter doesn't work for oo-install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 01:58 UTC by Ma xiaoqiang
Modified: 2016-07-04 00:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-28 15:30:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ma xiaoqiang 2015-10-13 01:58:03 UTC
Description of problem:
The '-t' parameter doesn't work for oo-install


Version-Release number of selected component (if applicable):
oo-install-3.0.3-1.el7aos.noarch

How reproducible:
100%


Steps to Reproduce:
1. run 'oo-install' as following
#oo-install -a openshift-ansible/ -t openshift-enterprise

Actual results:
TASK: [openshift_repos | assert ] ********************************************* 
failed: [10.66.79.193] => {"assertion": "openshift_deployment_type in known_openshift_deployment_types", "evaluated_to": false, "failed": true}

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************



Check the ansible hosts file, the deployment_type is set to None


Expected results:
1. Can install the env successfully
2. suggest to set default value for the '-t' parameter, or set it to required parameter for oo-install

Additional info:

Comment 2 Brenton Leanhardt 2015-10-28 15:30:59 UTC
oo-install was officially packaged and renamed to atomic-openshift-installer.  In the latest puddle you can install atomic-openshift-utils to provide that tool.


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