Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1512003 - Converting the Openshift Container Platform Registry with Container-Native Storage: Step 18 Sub-step i Documentation Issues
Summary: Converting the Openshift Container Platform Registry with Container-Native St...
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Container_Native_Storage_with_OpenShift
Version: cns-3.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: CNS 3.10
Assignee: Chandrakanth Pai
QA Contact: Ashmitha Ambastha
Depends On:
Blocks: 1568865 1573420
TreeView+ depends on / blocked
Reported: 2017-11-10 15:47 UTC by Ian Tewksbury
Modified: 2018-09-17 05:15 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-09-17 05:15:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1538262 None None None Never

Internal Links: 1538262

Description Ian Tewksbury 2017-11-10 15:47:51 UTC
Document URL:

Section Number and Name: 10.2. Step 18, sup step i: Converting the Openshift Container Platform Registry with Container-Native Storage

Describe the issue: 

The instructions do not work as written.

Step 18.i:

Make the old registry readonly by executing the following command:
# oc set env dc/docker-registry REGISTRY_STORAGE_MAINTENANCE_READONLY_ENABLED=true

This does not work due to

Suggestions for improvement: 

Should do one of the following:

1. note in the documentation that this step can't work until issue is fixed
2. provide another solution for marking the registry read only

Comment 2 Ian Tewksbury 2017-11-10 15:48:27 UTC
Additionally sub step vii does not work to disable Read Only mode.

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