Description of problem (please be detailed as possible and provide log
snippests):
During RDR deployment with globalnet, mon doesn't come up and service export is not created on one of the managed clusters after enabling multiclusterservice by editing the storage cluster CR.

And storage cluster remains in the error state.

pods|grep mon
rook-ceph-mon-d-67d746cd7f-8rmvv                                  2/2     Running            3 (147m ago)    17h   10.131.0.67   compute-1   <none>           <none>
rook-ceph-mon-e-5bc8d9f5f9-wrnlv                                  2/2     Running            2 (146m ago)    17h   10.129.2.67   compute-0   <none>           <none>


oc get serviceexport -n openshift-storage
NAME              AGE
rook-ceph-mon-d   17h
rook-ceph-mon-e   17h
rook-ceph-osd-0   17h
rook-ceph-osd-1   17h
rook-ceph-osd-2   17h


ODF logs from the cluster- http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/bz-aman/29sept24/

Version of all relevant components (if applicable):
ODF 4.17.0-111
OCP 4.17.0-0.nightly-2024-09-27-213503


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. Do RDR deployment with globalnet on VMware
2.
3.


Actual results: Mon doesn't come up and serviceexport is not created after enabling multiclusterservice


Expected results: Mon should come up and serviceexport should be successfully created after enabling multiclusterservice on a RDR setup


Additional info: