Bug 1687325

Summary: Commands missing from the document during upgrade of block provisioner image for independent mode
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Arun Kumar <arukumar>
Component: doc-Container_Native_Storage_with_OpenShiftAssignee: storage-doc
Status: CLOSED CURRENTRELEASE QA Contact: Aditya Ramteke <aramteke>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: asriram, kbg, knarra, pprakash, rhs-bugs, sankarshan, storage-doc, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.z Batch Update 3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-22 13:29:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1694089    

Description Arun Kumar 2019-03-11 09:23:28 UTC
Document URL:

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

Section Number and Name: 
7.2.4.Upgrading Gluster Block

Describe the issue: 

1. The following step is missing from the doc and It should be added after step 8 of the section: 
 
Delete the following resources from the old pod
# oc delete clusterroles.authorization.openshift.io glusterblock-provisioner-runner
# oc delete serviceaccounts glusterblock-registry-provisioner

Suggestions for improvement: 

This step should be added after the following step:

8. If OCS 3.10 is deployed via Ansible, depending on the OCP version, edit the glusterblock-provisioner template to change the IMAGE_NAME, IMAGE_VERSION and NAMESPACE.

Comment 3 RamaKasturi 2019-03-11 17:52:49 UTC
we see that this bug needs to be updated for both 3.10 & 3.11 docs in independent mode section.

Comment 5 RamaKasturi 2019-04-05 12:51:05 UTC
Acking this bug for 3.11.3