Bug 1259562 - [DOCS] Fix issue in Deploying Registry steps
Summary: [DOCS] Fix issue in Deploying Registry steps
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 04:53 UTC by Vikram Goyal
Modified: 2017-12-28 12:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-28 12:10:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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