Bug 2094272

Summary: [DDF] Add an example here, because it's not clear what is the syntax of "failed-osd-id1". It's the number only of the
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Agil Antony <agantony>
Component: documentationAssignee: Agil Antony <agantony>
Status: CLOSED CURRENTRELEASE QA Contact: Oded <oviner>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.9CC: agantony, asriram, ddf-bot, ebenahar, kramdoss, nberry, ocs-bugs, odf-bz-bot, prsurve, sagrawal
Target Milestone: ---   
Target Release: ODF 4.9.z Async   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2094271
: 2094273 (view as bug list) Environment:
Last Closed: 2023-03-09 12:47:11 UTC Type: ---
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: 1995530, 2094271, 2128435    
Bug Blocks: 2094273    

Comment 7 Oded 2022-11-20 13:44:53 UTC 
Doc fixed

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html-single/replacing_devices/index#replacing-operational-or-failed-storage-devices-on-vmware-infrastructure_rhodf
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html-single/replacing_nodes/index#replacing-an-operational-aws-node-upi_rhodf

Remove the old OSD from the cluster.

$ oc process -n openshift-storage ocs-osd-removal \
-p FAILED_OSD_IDS=<failed_osd_id> FORCE_OSD_REMOVAL=false | oc create -n openshift-storage -f -
<failed_osd_id>
Is the integer in the pod name immediately after the rook-ceph-osd prefix. You can add comma separated OSD IDs in the command to remove more than one OSD, for example, FAILED_OSD_IDS=0,1,2.