Bug 1264764 - oo-install couldn't configure deployment_type correctly when running unattended
oo-install couldn't configure deployment_type correctly when running unattended
Status: CLOSED CURRENTRELEASE
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.0.0
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Samuel Munilla
Gaoyun Pei
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-21 03:17 EDT by Gaoyun Pei
Modified: 2015-11-20 10:42 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-20 10:42:08 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)

  None (edit)
Comment 2 Gaoyun Pei 2015-09-21 23:18:15 EDT
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.