Bug 2117533

Summary:	[DDF] The documentation look completely clean.
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	documentation	Assignee:	Anjana Suparna Sriram <asriram>
Status:	NEW ---	QA Contact:	Neha Berry <nberry>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.8
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2022-08-11 09:13:46 UTC

The documentation look completely clean. 

It could be good to add details if the drive is failed for hw issue, if the drive need to be replaced before launching this procedure. 

It's the way I would understand it, reading it, but could be good to detail that it's safe to replace the drive after seeing that the reason of the CrashLoopBackOff is the drive.

Reported by: rhn-support-jpeyrard

https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.8/html/deploying_and_managing_openshift_container_storage_using_red_hat_openstack_platform/replacing-storage-devices_osp#annotations:07135afb-29b5-4c29-9b74-7f2a8cb0370c