Bug 1320017

Summary:	No OSE/AEP 3.2 product option in atomic-openshift-installer
Product:	OpenShift Container Platform	Reporter:	Gaoyun Pei <gpei>
Component:	Installer	Assignee:	Samuel Munilla <smunilla>
Status:	CLOSED ERRATA	QA Contact:	Ma xiaoqiang <xiama>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	ajia, aos-bugs, bleanhar, jokerman, mmccomas, xtian
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift-ansible-3.0.70-1.git.0.3f80411.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-12 16:39:01 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 Gaoyun Pei 2016-03-22 06:42:03 UTC

Description of problem:
OSE/AEP 3.2 option for installation is not shown in the installer, but we now should support that.


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.62-1.git.0.394cb87.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Run 'atomic-openshift-installer install'


Actual results:
Which variant would you like to install?


(1) OpenShift Enterprise 3.1
(2) OpenShift Enterprise 3.0
(3) Atomic Enterprise Platform 3.1

Choose a variant from above:  [1]: 



Expected results:
Should have OSE/AEP 3.2 choice

Additional info:

Comment 2 Gaoyun Pei 2016-04-05 02:53:16 UTC

Verify this bug with atomic-openshift-utils-3.0.71-1.git.0.63af28f.el7.noarch

There're five product choices now and OSE-3.2 is the default one. Tried option (1) & (4), both work well.


Which variant would you like to install?


(1) OpenShift Enterprise 3.2
(2) OpenShift Enterprise 3.1
(3) OpenShift Enterprise 3.0
(4) Atomic Enterprise Platform 3.2
(5) Atomic Enterprise Platform 3.1

Choose a variant from above:  [1]:

Comment 4 errata-xmlrpc 2016-05-12 16:39:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1065