-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
odf-4.15
-
None
Describe the issue:
We don't recommend enabling FORCE_OSD_REMOVAL until the OSD can be removed gracefully.
The osd removal job can take time as the data on the OSD (being removed) needs to be backfilled to other available OSD's.
If the ocs-osd-removal-job does not move to Completed state after more than 10 minutes, delete the JOB ["oc delete -n openshift-storage job ocs-osd-removal-job"] and enable the FORCE_OSD_REMOVAL flag
[oc process -n openshift-storage ocs-osd-removal -p FAILED_OSD_IDS=${osd_id_to_remove} FORCE_OSD_REMOVAL=true |oc create -n openshift-storage -f -]
Describe the task you were trying to accomplish:
Suggestions for improvement:
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.14/html-single/replacing_devices/index#replacing-operational-or-failed-storage-devices-on-vmware-infrastructure_rhodf
Chapter/Section Number and Title:
Chapter 2.1 section 4
"Remove the old OSD from the cluster so that you can add a new OSD."
Product Version:
Environment Details: All
Any other versions of this document that also needs this update:
Additional information:
- links to
-
RHBA-2024:139715 Red Hat OpenShift Data Foundation 4.15.8 security and bug fix update