Bug 2233010 - [RDR] Replace existing OSDs to use bluestore-rdr store
Summary: [RDR] Replace existing OSDs to use bluestore-rdr store
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.15.0
Assignee: Santosh Pillai
QA Contact: Pratik Surve
URL:
Whiteboard:
Depends On:
Blocks: 2246375
TreeView+ depends on / blocked
 
Reported: 2023-08-21 04:18 UTC by Santosh Pillai
Modified: 2024-03-19 15:23 UTC (History)
5 users (show)

Fixed In Version: 4.15.0-103
Doc Type: Enhancement
Doc Text:
.Ability to use bluestore-rdr as object storage device backing store OpenShift Data Foundation provides the ability to use `bluestore-rdr` as the object storage device (OSD) backing store for the Brownfield customers. This `bluestore-rdr` has improved performance over bluestore backend store, which is important when the cluster is required to be used for Regional Disaster Recovery (RDR). Also, it is possible to migrate the OSDs to `bluestore-rdr` from the user interface.
Clone Of:
Environment:
Last Closed: 2024-03-19 15:22:52 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 510 0 None open bug 2233010: replace osd to use new backend store 2023-08-21 13:31:05 UTC
Red Hat Product Errata RHSA-2024:1383 0 None None None 2024-03-19 15:23:00 UTC

Description Santosh Pillai 2023-08-21 04:18:05 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
For existing RDR customers, allow replacing existing OSDs to create new ones using bluestore-rdr

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:
Comment 9 errata-xmlrpc 2024-03-19 15:22:52 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 (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix 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/RHSA-2024:1383
Note You need to log in before you can comment on or make changes to this bug.