Bug 1259562 - [DOCS] Fix issue in Deploying Registry steps
[DOCS] Fix issue in Deploying Registry steps
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2015-09-03 00:53 EDT by Vikram Goyal
Modified: 2017-12-28 07:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-28 07:10:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vikram Goyal 2015-09-03 00:53:00 EDT
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

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.
Comment 3 Vikram Goyal 2017-12-28 07:10:03 EST
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.