Bug 2027396 - [4.9.z clone] [Data Loss] Use ceph 'osd safe-to-destroy' and 'osd ok-to-stop' feature in OSD purge job
Summary: [4.9.z clone] [Data Loss] Use ceph 'osd safe-to-destroy' and 'osd ok-to-stop'...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.9.11
Assignee: Travis Nielsen
QA Contact: Rachael
URL:
Whiteboard:
Depends On: 2026007
Blocks: 2027826 2054518 2119510 2120260
TreeView+ depends on / blocked
 
Reported: 2021-11-29 14:33 UTC by Sébastien Han
Modified: 2023-08-09 17:03 UTC (History)
17 users (show)

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.
Clone Of: 2026007
Environment:
Last Closed: 2022-09-26 16:46:45 UTC
Embargoed:
kramdoss: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 399 0 None open Bug 2027396: Require force flag to purge an OSD if data may be lost 2022-08-23 11:17:43 UTC
Red Hat Product Errata RHBA-2022:6718 0 None None None 2022-09-26 16:47:30 UTC

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
Note You need to log in before you can comment on or make changes to this bug.