Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1421987 - [3.6] The registry-console should be updated by upgrade playbook
[3.6] The registry-console should be updated by upgrade playbook
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.6.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: ewolinet
Anping Li
:
Depends On:
Blocks: 1454786 1454787
  Show dependency treegraph
 
Reported: 2017-02-14 04:36 EST by Anping Li
Modified: 2017-08-16 15 EDT (History)
5 users (show)

See Also:
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:
: 1454786 1454787 (view as bug list)
Environment:
Last Closed: 2017-08-10 01:17:28 EDT
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 RHEA-2017:1716 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 05:02:50 EDT

  None (edit)
Description Anping Li 2017-02-14 04:36:03 EST
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 18:18:44 EDT
Able to recreate this upgrading a 3.4 system to 3.5
Comment 9 Anping Li 2017-06-09 06:01:00 EDT
Verified and pass on oepnshift-ansible-3.6.89.4
Comment 11 errata-xmlrpc 2017-08-10 01:17:28 EDT
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

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