Bug 1497041

Summary: 3.7 installer is setting default image version for service catalog image to v3.6
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: InstallerAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: high    
Version: 3.7.0CC: aos-bugs, jokerman, jpeeler, mmccomas, pmorie, sdodson, wmeng
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:13:20 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:
Embargoed:

Description Johnny Liu 2017-09-29 05:16:11 UTC
Description of problem:
see the following details

Version-Release number of the following components:
openshift-ansible-3.7.0-0.134.0.git.0.6f43fc3.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Enable service catalog in inventory host file:
openshift_enable_service_catalog=true
openshift_template_service_broker_namespaces=['openshift']
openshift_service_catalog_image_prefix=openshift3/ose-
2. Trigger installation
3.

Actual results:
Check service catalog's image tag:
# oc edit ds apiserver
<--snip-->
        image: openshift3/ose-service-catalog:v3.6
<--snip-->

Expected results:
<--snip-->
        image: openshift3/ose-service-catalog:v3.7
<--snip-->

Additional info:
The root cause in code:
$ cat roles/openshift_service_catalog/vars/openshift-enterprise.yml
---
__openshift_service_catalog_image_prefix: "registry.access.redhat.com/openshift3/ose-"
__openshift_service_catalog_image_version: "v3.6"

Comment 3 Johnny Liu 2017-10-11 03:36:57 UTC
Verified this bug with openshift-ansible-3.7.0-0.143.2.git.0.39404c5.el7.noarch, and PASS.

Comment 7 errata-xmlrpc 2017-11-28 22:13:20 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/RHSA-2017:3188