Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1452214

Summary:	registry-console not starting - dc points to openshift3/registry-console:3.6, actual image is openshift3/registry-console:v3.6
Product:	OpenShift Container Platform	Reporter:	Mike Fiedler <mifiedle>
Component:	Release	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Mike Fiedler <mifiedle>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, jialiu, jokerman, jupierce, mifiedle, mmccomas, wmeng
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	3.7.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 21:55:46 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:

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