Bug 2306387 - cephblockpool: allow editing the mirroring field from different controller
Summary: cephblockpool: allow editing the mirroring field from different controller
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.17
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ODF 4.17.0
Assignee: Rewant
QA Contact: Amrita Mahapatra
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-21 06:31 UTC by Rewant
Modified: 2024-10-30 14:31 UTC (History)
4 users (show)

Fixed In Version: 4.17.0-101
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-10-30 14:31:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 2755 0 None open Bug 2306387:[release-4.17] storagecluster: rewrite cephblockpool reconcilation 2024-08-21 07:08:29 UTC
Github red-hat-storage ocs-operator pull 2796 0 None open Bug 2306387: [release-4.17] update the cephblockpool reconciler to disable mirroring 2024-09-13 12:42:32 UTC
Red Hat Issue Tracker OCSBZM-8801 0 None None None 2024-08-21 06:33:58 UTC
Red Hat Product Errata RHSA-2024:8676 0 None None None 2024-10-30 14:31:42 UTC

Description Rewant 2024-08-21 06:31:58 UTC
Description of problem (please be detailed as possible and provide log
snippests):
The current storageCluster reconcile is written in such a way that it resets all the fields of the cephblockpool.
This will not allow us to edit the mirroring field from another component. Rewrite the controller in a way that it
allows us to edit the mirroring field from other components when mirroring field is not set on the storage cluster CR.

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 7 Sunil Kumar Acharya 2024-09-03 05:33:26 UTC
Please update the RDT flag/text appropriately.

Comment 13 errata-xmlrpc 2024-10-30 14:31:39 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.17.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:8676


Note You need to log in before you can comment on or make changes to this bug.