Bug 1839212 - [Doc] Incorrect command in OCS deployment guide
Summary: [Doc] Incorrect command in OCS deployment guide
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: RHGS 3.5.z Batch Update 3
Assignee: Agil Antony
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1845059
TreeView+ depends on / blocked
 
Reported: 2020-05-22 18:39 UTC by Sonal
Modified: 2020-07-01 10:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-25 10:03:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Sonal 2020-05-22 18:39:25 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/index#upgrading_if_existing_version_deployed_by_using_cns_deploy

Section Number and Name: 

6.1.3.2. Upgrading the Red Hat Gluster Storage Pods

6.1.4.2. Upgrading the Red Hat Gluster Storage Pods

6.2.3.2. Upgrading the Red Hat Gluster Storage Registry Pods

6.2.4.2. Upgrading the Red Hat Gluster Storage Registry Pods

Describe the issue: 

The below command mentioned in the deployment doc is incorrect:

~~~
# for eachVolume in gluster volume list; do echo $eachVolume; gluster volume set $eachVolume server.tcp-user-timeout 42 ; done

For example:

# for eachVolume in gluster volume list; do echo $eachVolume; gluster volume set $eachVolume server.tcp-user-timeout 42 ; done
  volume1
  volume set: success
  volume2
  volume set: success
~~~

This command is mentioned multiple times in the doc. All the section numbers containing command is mentioned above.

Suggestions for improvement: 

It should be:

# for eachVolume in $(gluster volume list); do echo $eachVolume; gluster volume set $eachVolume server.tcp-user-timeout 42 ; done


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