Bug 1259562

Summary:	[DOCS] Fix issue in Deploying Registry steps
Product:	OpenShift Container Platform	Reporter:	Vikram Goyal <vigoyal>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED NOTABUG	QA Contact:	Vikram Goyal <vigoyal>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	3.0.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-28 12:10:03 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 Vikram Goyal 2015-09-03 04:53:00 UTC

From: https://github.com/openshift/openshift-docs/issues/876

I recently came across trying to create a registry using the step located in the docs:
oadm registry --config=/etc/openshift/master/admin.kubeconfig
--credentials=/etc/openshift/master/openshift-registry.kubeconfig
--images='registry.access.redhat.com/openshift3/ose-${component}:${version}'

The ${components/version} variables were not set resulting in my pod failing to pull image 'registry.access.redhat.com/openshift3/ose-:'.

Removing the --image parameter fixed this and pulled the docker-registry:v3.0.1.0. However, in the docs it says it a required parameter.

Are ${component}:${version} not necessary anymore? Docs may need to be updated.
https://access.redhat.com/documentation/en/openshift-enterprise/version-3.0/openshift-enterprise-30-administrator-guide/chapter-1-installing

Comment 3 Vikram Goyal 2017-12-28 12:10:03 UTC

As per https://github.com/openshift/openshift-docs/issues/876#issuecomment-130435872, this is expected behavior.

Closing this bug.