Bug 1419493 - [3.4] Installer pulls in 3.3 registry-console image
Summary: [3.4] Installer pulls in 3.3 registry-console image
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-06 10:46 UTC by Marko Myllynen
Modified: 2017-03-06 16:38 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2017-03-06 16:38:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0448 0 normal SHIPPED_LIVE Important: ansible and openshift-ansible security and bug fix update 2017-03-06 21:36:25 UTC

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


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