Bug 1421987

Summary:	[3.6] The registry-console should be updated by upgrade playbook
Product:	OpenShift Container Platform	Reporter:	Anping Li <anli>
Component:	Cluster Version Operator	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, bleanhar, ewolinet, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: As part of an upgrade the registry-console wasn't having its image version bumped Consequence: After an upgrade, the registry-console version was still the previous one. Fix: Along with the docker registry and router, we update the image version for the registry-console. Result: When doing an upgrade, the version of the registry-console should be incremented to match the version upgraded to.	Story Points:	---
Clone Of:
Clones:	1454786 1454787 (view as bug list)		Environment:
Last Closed:	2017-08-10 05:17:28 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:
Bug Depends On:
Bug Blocks:	1454786, 1454787

Description Anping Li 2017-02-14 09:36:03 UTC

Description of problem:
After upgrade, the registry-console still use old image.  Since registry-console was installed by default.  The upgrade playbook should update registry-console dc to use same version with docker-registry.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install OCP 3.4. The registry-console is using v3.3
2. Upgrade to OCP 3.5 by ansible-playbook
   The registry-console version is still v3.3

Actual results:


Expected results:
The image version should be updated to use same version with docker-registry. At least it should use the openshift_release version

Additional info:

Comment 1 ewolinet 2017-05-09 22:18:44 UTC

Able to recreate this upgrading a 3.4 system to 3.5

Comment 9 Anping Li 2017-06-09 10:01:00 UTC

Verified and pass on oepnshift-ansible-3.6.89.4

Comment 11 errata-xmlrpc 2017-08-10 05:17:28 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/RHEA-2017:1716