Description of problem (please be detailed as possible and provide log snippets): multicluster-orchestrator resets `spec.network.multiClusterService.Enabled` field when it updates StorageCluster to configure Disaster Recovery. Version of all relevant components (if applicable): > v4.13.0 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? > It impacts DR feature testing. Is there any workaround available to the best of your knowledge? > Yes, scaling down multicluster-orchestrator pods on all clusters. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? > 1 Is this issue reproducible? > Yes Can this issue reproduce from the UI? > Yes If this is a regression, please provide more details to justify this: It is due to an API change in ocs-operator. Not a regression. Steps to Reproduce: 1. Set spec.network.multiClusterService.Enabled: true on StorageCluster 2. Create MirrorPeer on hub pointing to these clusters 3. Actual results: spec.network.multiClusterService.Enabled gets removed. Expected results: spec.network.multiClusterService.Enabled should not be removed. Additional info:
This bug was initially part of https://bugzilla.redhat.com/show_bug.cgi?id=2183177. Moving it out to separately track the individual changes.
Fixed in 4.13.0-130
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.13.0 enhancement and 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/RHBA-2023:3742