Bug 1264764 - oo-install couldn't configure deployment_type correctly when running unattended
Summary: oo-install couldn't configure deployment_type correctly when running unattended
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-21 07:17 UTC by Gaoyun Pei
Modified: 2015-11-20 15:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-20 15:42:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Gaoyun Pei 2015-09-22 03:18:15 UTC 
Verify this bug with oo-install-ose-20150921-1823

Configure "deployment_type: xxx" in installer.cfg.yaml, ansible inventory could be written correctly.

When not configure "deployment_type: xxx" in installer.cfg.yaml, --deployment-type could also write ansible inventory correctly.

And --deployment-type has higher priority than the deployment_type: setting in installer.cfg.yaml.
Note You need to log in before you can comment on or make changes to this bug.