Bug 2120260
| Summary: | [4.9.z clone] OSD Removal template needs to expose option to force remove the OSD | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Subham Rai <srai> |
| Component: | ocs-operator | Assignee: | Subham Rai <srai> |
| Status: | CLOSED ERRATA | QA Contact: | Rachael <rgeorge> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | ikave, jarrpa, kbg, kramdoss, madam, mmuench, muagarwa, nberry, ocs-bugs, odf-bz-bot, rcyriac, rgeorge, sostapov, srai, tnielsen |
| Target Milestone: | --- | Keywords: | AutomationBackLog |
| Target Release: | ODF 4.9.11 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 2027826 | 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: | 2027396, 2027826 | ||
| Bug Blocks: | 2054518, 2119525 | ||
|
Comment 5
Travis Nielsen
2022-08-22 16:27:55 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 |