Bug 2120260 - [4.9.z clone] OSD Removal template needs to expose option to force remove the OSD
Summary: [4.9.z clone] OSD Removal template needs to expose option to force remove the...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.9.11
Assignee: Subham Rai
QA Contact: Rachael
URL:
Whiteboard:
: 2119510 (view as bug list)
Depends On: 2027396 2027826
Blocks: 2054518 2119525
TreeView+ depends on / blocked
 
Reported: 2022-08-22 11:17 UTC by Subham Rai
Modified: 2023-08-09 17:00 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
With this update, you can set a flag, `true` or `false` to indicate whether the OSD can be forcefully removed or not. By default, the flag is set to `false` and this ensures that there is no data loss due to accidental removal of the OSD. When the OSD removal fails and and if you are sure that the OSD needs to be removed, then you set the flag to `true` and run the job again.
Clone Of: 2027826
Environment:
Last Closed: 2022-09-26 16:46:45 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 1778 0 None open Bug 2120260:[release-4.9] expose option to force remove the OSD in osd removal template 2022-08-23 07:24:22 UTC
Red Hat Product Errata RHBA-2022:6718 0 None None None 2022-09-26 16:47:30 UTC

Comment 5 Travis Nielsen 2022-08-22 16:27:55 UTC 
*** Bug 2119510 has been marked as a duplicate of this bug. ***
Comment 15 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.