Bug 1619405 - [3.9] Registry Console Not Upgraded to Current Version During Upgrade
Summary: [3.9] 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.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.z
Assignee: Russell Teague
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1611818 1619408
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-20 18:30 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-22 04:53:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2658 0 None None None 2018-09-22 04:53:57 UTC

Comment 1 Russell Teague 2018-08-20 18:42:09 UTC 
release-3.9: https://github.com/openshift/openshift-ansible/pull/9678
Comment 2 Russell Teague 2018-08-29 20:05:57 UTC 
Waiting for 3.9 build

git tag --contains ad410b99ac52ff124036c56c2cf53579375fb879
Comment 4 Johnny Liu 2018-09-07 08:54:24 UTC 
Verified this bug with openshift-ansible-3.9.42-1.git.0.6598f8f.el7.noarch, and PASS.

Before upgrade:
[root@ip-172-18-1-102 ~]# oc describe po registry-console-1-t67m8|grep Image:
    Image:          registry.reg-aws.openshift.com:443/openshift3/registry-console:v3.9

Did a minor upgrade.

After upgrade:
# oc describe pod registry-console-2-c69t4|grep Image
    Image:          registry.reg-aws.openshift.com:443/openshift3/registry-console:v3.9.42
Comment 6 errata-xmlrpc 2018-09-22 04:53:09 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:2658
Note You need to log in before you can comment on or make changes to this bug.