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

When trying to deploy ODF to an IBM IPI cluster using a COS-backed backingstore, Noobaa becomes stuck in the Configuring state. 

-----------------
  phase: Configuring
  readme: "\n\n\tNooBaa operator is still working to reconcile this system.\n\tCheck
    out the system status.phase, status.conditions, and events with:\n\n\t\tkubectl
    -n openshift-storage describe noobaa\n\t\tkubectl -n openshift-storage get noobaa
    -o yaml\n\t\tkubectl -n openshift-storage get events --sort-by=metadata.creationTimestamp\n\n\tYou
    can wait for a specific condition with:\n\n\t\tkubectl -n openshift-storage wait
    noobaa/noobaa --for condition=available --timeout -1s\n\n\tNooBaa Core Version:
    \    master-20230920\n\tNooBaa Operator Version: 5.15.0\n"
  services:
-----------------
  - lastHeartbeatTime: "2023-12-18T10:39:32Z"
    lastTransitionTime: "2023-12-18T10:30:28Z"
    message: |-
      RequestError: send request failed
      caused by: Put "https://s3.direct..cloud-object-storage.appdomain.cloud/nb.1702895972648.apps.jnk-pr9072b6235.ibmcloud2.qe.rh-ocs.com": dial tcp: lookup s3.direct..cloud-object-storage.appdomain.cloud: no such host
    reason: TemporaryError
-----------------


Version of all relevant components (if applicable):
Server Version: 4.15.0-0.nightly-2023-12-19-033450


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, Noobaa is unable to be installed for this scenario (IBM IPI with COS-backed backingstore).


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?
unknown


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


Steps to Reproduce:
1. Deploy OCP to IBM Cloud(IPI)
2. Label worker nodes with region information
'oc label node <worker name> ibm-cloud\.kubernetes\.io/region=<REGION>' in our case <REGION> is us-south.
3. Deploy ODF, creating the Secret via YAML as described here:
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html-single/deploying_and_managing_openshift_data_foundation_using_google_cloud/index#creating-an-IBM-COS-backed-backingstore_rhodf


Actual results:
Noobaa is stuck in Creating phase.


Expected results:
Noobaa creation is successful, deployment succeeds.


Additional info:

https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html-single/deploying_and_managing_openshift_data_foundation_using_google_cloud/index#creating-an-IBM-COS-backed-backingstore_rhodf

noobaa operator logs: https://url.corp.redhat.com/d7c188f

noobaa.yaml: https://url.corp.redhat.com/a9c0127

full ocs must gather: https://url.corp.redhat.com/b9c7f09