Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1419493 - [3.4] Installer pulls in 3.3 registry-console image
[3.4] Installer pulls in 3.3 registry-console image
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.4.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.4.z
Assigned To: Scott Dodson
Johnny Liu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-02-06 05:46 EST by Marko Myllynen
Modified: 2017-03-06 11:38 EST (History)
5 users (show)

See Also:
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 11:38:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0448 normal SHIPPED_LIVE Important: ansible and openshift-ansible security and bug fix update 2017-03-06 16:36:25 EST

  None (edit)
Description Marko Myllynen 2017-02-06 05:46:33 EST
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 05:29:13 EST
Very much related, perhaps even a dupe:

https://bugzilla.redhat.com/show_bug.cgi?id=1383275
Comment 8 errata-xmlrpc 2017-03-06 11:38:19 EST
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.