Bug 1619408 - [3.10] Registry Console Not Upgraded to Current Version During Upgrade
Summary: [3.10] Registry Console Not Upgraded to Current Version During Upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.10.z
Assignee: Russell Teague
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1611818 1618659
Blocks: 1619405
TreeView+ depends on / blocked
 
Reported: 2018-08-20 18:31 UTC by Russell Teague
Modified: 2021-09-09 15:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Image definition for registry-console was using a variable that only specified a major.minor. Updated to use openshift_image_tag which specifies the full major.minor.patch version.
Clone Of: 1611818
Environment:
Last Closed: 2018-09-04 07:10:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2578 0 None None None 2018-09-04 07:11:05 UTC

Comment 1 Russell Teague 2018-08-20 18:40:57 UTC 
release-3.10: https://github.com/openshift/openshift-ansible/pull/9677
Comment 2 Russell Teague 2018-08-23 12:51:09 UTC 
openshift-ansible-3.10.35-1
Comment 4 Johnny Liu 2018-08-30 07:41:23 UTC 
Verified this bug with openshift-ansible-3.10.41-1.git.0.fd15dd7.el7.noarch, and PASS.

Before upgrade, 
[root@qe-jialiu3102-master-etcd-1 ~]# oc describe po registry-console-1-5jgjl |grep Image
    Image:          registry.reg-aws.openshift.com:443/openshift3/registry-console:v3.10


After did a minor version upgrade with a specific openshift_image_tag setting,
[root@qe-jialiu3102-master-etcd-1 ~]# oc describe po registry-console-2-wcpjq|grep Image
    Image:          registry.reg-aws.openshift.com:443/openshift3/registry-console:v3.10.34
Comment 6 errata-xmlrpc 2018-09-04 07:10:49 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-2018:2578
Note You need to log in before you can comment on or make changes to this bug.