Bug 1419493

Summary: [3.4] Installer pulls in 3.3 registry-console image
Product: OpenShift Container Platform Reporter: Marko Myllynen <myllynen>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: aos-bugs, aweiteka, jialiu, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The installer that shipped with OCP 3.4 did not update the registry console template to use the latest version of the console image. This has been corrected so that new installs use the latest console image.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-06 16:38:19 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 Marko Myllynen 2017-02-06 10:46:33 UTC
Description of problem:
After successful OCP 3.4 installation we see:

[root@master01 ~]# oc get all
NAME                  DOCKER REPO                                    TAGS      UPDATED
is/registry-console   172.30.192.143:5000/default/registry-console   3.3

3.3 was not set anywhere in the Ansible inventory.

Comment 4 Marko Myllynen 2017-02-08 10:29:13 UTC
Very much related, perhaps even a dupe:

https://bugzilla.redhat.com/show_bug.cgi?id=1383275

Comment 8 errata-xmlrpc 2017-03-06 16:38:19 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:0448