This bug was initially created as a copy of Bug #2187952

I am copying this bug because: 



Description of problem (please be detailed as possible and provide log
snippests):

Hi, when we try to deploy vSphere UPI stretch cluster arbiter cluster with latest ODF 4.13-168 builds, there seems to be some issue with rook-ceph-operator pod and the deployments are failing to complete. rook-ceph-operator-* pod is in CrashLoopBackOff state with following error:

Last State:     Terminated
      Reason:       Error
      Message:      failed to run operator: gave up to run the operator manager: failed to set up overall controller-runtime manager: error listening on :8080: listen tcp :8080: bind: address already in use
      Exit Code:    1




Version of all relevant components (if applicable):
ODF 4.13-168

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
yes

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:
yes

Steps to Reproduce:
1. Deploy stretch cluster with arbiter using latest ODF 4.13 builds
2. 
3.


Actual results:
Deployments are failing

Expected results:
Deployments should succeed

Additional info:

Live-cluster: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/mashetty-s1/mashetty-s1_20230419T042248/openshift-cluster-dir/auth/kubeconfig