Bug 1299322 - "container" option doesn't work well in atomic-openshift-installer
Summary: "container" option doesn't work well in 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
high
high
Target Milestone: ---
: ---
Assignee: Samuel Munilla
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 06:26 UTC by Gaoyun Pei
Modified: 2016-07-04 00:44 UTC (History)
5 users (show)

Fixed In Version: openshift-ansible-3.0.34-1.git.0.b0511f9.el7aos
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 20:58:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gaoyun Pei 2016-01-18 06:26:10 UTC
Description of problem:

Install an env with atomic-openshift-installer, choosing "container" in step "Will this host be RPM or Container based (rpm/container)?".

"containerized: true" would be written into installer.cfg.yml, but there's no containerized configuration generated in ~/.config/openshift/.ansible/hosts.

So the installer won't work when trying to install container env on RHEL-7 hosts.


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.33-1.git.0.bb1f8aa.el7aos.noarch

How reproducible:
Always

Steps to Reproduce:
1.Install containerized env by choosing "container" with atomic-openshift-installer


Actual results:
It didn't run a containerized installation.


Expected results:
Should have "containerized=True" in ansible inventory when choosing "container".

Additional info:

Comment 1 Samuel Munilla 2016-01-18 19:31:25 UTC
Should be fixed by: https://github.com/openshift/openshift-ansible/pull/1205

Comment 3 Gaoyun Pei 2016-01-19 04:18:07 UTC
Test with atomic-openshift-utils-3.0.35-1.git.0.6a386dd.el7aos.noarch

Once choose container install method, containerized=True would be set for the host.


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