Bug 1843482

Summary: Docs: multiple changes needed in Section 8.3.1 of Managing guide to sync it with sections 8.3.2 and 8.3.3 for other LSO infrastructures
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Neha Berry <nberry>
Component: documentationAssignee: Olive Lakra <olakra>
Status: CLOSED CURRENTRELEASE QA Contact: Sidhant Agrawal <sagrawal>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: asriram, ebenahar, edonnell, ocs-bugs, olakra, ratamir, sagrawal
Target Milestone: ---   
Target Release: ---   
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: 2020-09-20 15:21:39 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: 1849769    
Bug Blocks:    

Description Neha Berry 2020-06-03 11:59:03 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=1803733

Description of problem (please be detailed as possible and provide log
snippests):
----------------------------------------------------------------------
For Node replacement on BM and VMware LSO, a lot of changes were suggested and incorporated in section 8.3.2 and 8.3.3 via Bug 1803733

But section 8.3.1. Replacing failed storage nodes on Amazon EC2 infrastructure was changed as per instructions in https:Bug 1818693#c9 much prior to the new changes in Bug 1803733

Hence, it would be good to make similar changes to Section 8.3.1 to match as much as possible with 8.3.2 and 8.3.3

We might have to remove some steps and add the new steps and then test the whole thing to confirm its working

Some other small changes:
------------------------------

1. Since we have the step for CSR approval in current 8.3.1, we need to change title of  8.3.1 as:

--->  8.3.1. Replacing failed storage nodes on Amazon EC2 user-provisioned infrastructure 

>> Step 15 iii) Display PVs with local-block.

$ oc get pv | grep local-block

---> the sc name is localblock (as seen in the exapmple output just below this command, hence replace local-block with localblock)

>> Step 15 i

Need to change the statement as we would be adding only one new device-by-id and not 3.. We can sync up on this


>> Step 15 iii

Example output should use 2328Gi instead of  1769Gi 

>> Step 18 Verify that the OSD is removed successfully by displaying the logs.

$ oc logs -n openshift-storage ocs-osd-removal-${failed_osd_id}-<pod-suffix>


lets sync up for the suggested steps and then we can test and proviasically, all the changes we suggested for Bug 1803733 would somehow be applicable for 8.3.1 (with a few exceptions)



Version of all relevant components (if applicable):
----------------------------------------------------------------------
OCS 4.4
Comment 2 Neha Berry 2020-06-03 12:03:08 UTC 
Link to Managing guide 

https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.4/html-single/managing_openshift_container_storage/index?lb_target=preview#scaling-up-storage-by-adding-capacity-to-your-openshift-container-storage-nodes-using-local-storage-devices_rhocs
Comment 8 Olive Lakra 2020-07-06 10:13:03 UTC 
Received modification request over ghat from Sidhant Agrawal
,
Updated the example output of step 9ii as follows ---> change ocs-deviceset-0-0-6j9zf to ocs-deviceset-0-0-nvs68 because we are showing ocs-deviceset-0-0-nvs68 in other steps

Preview URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.4/html-single/managing_openshift_container_storage/index?lb_target=preview#replacing-failed-storage-nodes-on-amazon-ec2-infrastructure_rhocs