Bug 2027396

Summary:	[4.9.z clone] [Data Loss] Use ceph 'osd safe-to-destroy' and 'osd ok-to-stop' feature in OSD purge job
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Sébastien Han <shan>
Component:	rook	Assignee:	Travis Nielsen <tnielsen>
Status:	CLOSED ERRATA	QA Contact:	Rachael <rgeorge>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	bkunal, ebenahar, karthickdoss, kbg, kramdoss, madam, muagarwa, nberry, ocs-bugs, odf-bz-bot, owasserm, rcyriac, rgeorge, shan, sheggodu, tnielsen, vumrao
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	ODF 4.9.11	Flags:	kramdoss: needinfo+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	With this enhancement, OSDs cannot be purged unless all the data (PGs) from the OSD is already recovered to other OSDs or the --force flag is passed to the OSD removal job. This avoids the risk of data loss particularly if multiple OSDs are removed at the same time.	Story Points:	---
Clone Of:	2026007	Environment:
Last Closed:	2022-09-26 16:46:45 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:	2026007
Bug Blocks:	2027826, 2054518, 2119510, 2120260

Comment 5 Travis Nielsen 2022-02-14 16:37:46 UTC

Closing for 4.9 since it's a big change across rook, ocs operator, and docs that needs to stabilize in 4.10.

Comment 6 Travis Nielsen 2022-08-17 13:50:13 UTC

Reopening per discussion to backport all the way to 4.6.z

Comment 19 errata-xmlrpc 2022-09-26 16:46:45 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenShift Data Foundation 4.9.11 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:6718