Bug 1452214 - registry-console not starting - dc points to openshift3/registry-console:3.6, actual image is openshift3/registry-console:v3.6
Summary: registry-console not starting - dc points to openshift3/registry-console:3.6,...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Release
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.7.0
Assignee: ewolinet
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-18 15:02 UTC by Mike Fiedler
Modified: 2017-11-28 21:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
As part of the resolution for bz 1421987, we updated the image for the registry-console when running the upgrade playbook. The image version being set was slightly incorrect and this resolved it.
Clone Of:
Environment:
Last Closed: 2017-11-28 21:55:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Description Mike Fiedler 2017-05-18 15:02:46 UTC 
Description of problem:

The registry-console is not starting after install in 3.6.75.   The dc is pointing to  registry.ops.openshift.com/openshift3/registry-console:3.6 but the actual image on the ops mirror is registry.ops.openshift.com/openshift3/registry-console:v3.6

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


How reproducible: Always


Workaround is to modify the dc.
Comment 1 Scott Dodson 2017-05-18 22:17:03 UTC 
I'm pretty sure by the time the image lands on registry.access.redhat.com it will have both '3.6' and 'v3.6' as the tags but it's my understanding that the latter is preferred. I think we special cased this already for enterprise versus origin so may as well stick the v in front.
Comment 5 Mike Fiedler 2017-06-20 02:55:08 UTC 
Verified on 3.6.114
Comment 9 errata-xmlrpc 2017-11-28 21:55:46 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/RHSA-2017:3188
Note You need to log in before you can comment on or make changes to this bug.