Bug 1719122 - Issues with document to upgrade cns-deploy based deployments - Section 6.1.3 and 6.2.3
Summary: Issues with document to upgrade cns-deploy based deployments - Section 6.1.3 ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 3.11.z Batch Update 3
Assignee: Chandrakanth Pai
QA Contact: Ashmitha Ambastha
URL:
Whiteboard:
Depends On:
Blocks: 1694089
TreeView+ depends on / blocked
 
Reported: 2019-06-11 06:14 UTC by Ashmitha Ambastha
Modified: 2019-07-22 13:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-22 13:31:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Ashmitha Ambastha 2019-06-11 06:14:59 UTC
Version-Release number of selected component (if applicable): 3.11.3 STAGE docs

In the STAGE docs, 

Section 6.2.3.1, is missing the command to update cns-deploy and heketi-client. The command is available in the existing LIVE doc. 
This change could have been caused by  https://bugzilla.redhat.com/show_bug.cgi?id=1717751

Section 6.2.3.1, point #4, should have not have the secret written like this - heketi-registry-admin-secret , the secret is created by the user. 
Add command to list the secrets and then edit the existing command accordingly. 
command should look like this - 
oc get secret <heketi-admin-secret-name> -o jsonpath='{.data.key}'|base64 -d;echo

Section 6.2.3.1, point #8, the name of the secret should not be given like such. 
The secret name heketi-registry-config-secret has to be edited into the existing command by the user.
command should look like this - 
# oc create secret generic <heketi-config-secret> --from-file=heketi.json

Section 6.2.3.1, point #9, 
For cns-deploy based deployments, it won't be heketi-registry. 
Change needs to be made in the following command -  #oc delete deploymentconfig,service,route heketi-registry

Section 6.2.3.1, point #12, 
oc get pods output for all the OCS pods running should not be pod names with registry. Please make change in the example. 

In Section 6.2.3.2, point #2,
Give output of the command #oc get ds , as the ds is used in the next step. 

In Section 6.2.3.2, point #3, 
the example for deleting glusterfs ds with --cascade=false should have the correct ds name. 
command should be like this -
oc delete ds glusterfs --cascade=false

In Section 6.2.3.2, point #4,
Edit the oc get pods output. It should not have registry.


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