Description of problem (please be detailed as possible and provide log snippests): In External mode deployment, noobaa is in Configuring stage Version of all relevant components (if applicable): ocs-registry:4.12.3-17 openshift installer (4.12.0-0.nightly-2023-05-17-133811) 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)? 1 Can this issue reproducible? 2/2 Can this issue reproduce from the UI? Not tried If this is a regression, please provide more details to justify this: Yes Steps to Reproduce: 1. install ODF in external mode using ocs-ci 2. check noobaa is in Ready state 3. Actual results: $ oc get noobaa NAME S3-ENDPOINTS STS-ENDPOINTS IMAGE PHASE AGE noobaa ["https://10.1.112.190:31636"] ["https://10.1.112.190:31867"] quay.io/rhceph-dev/odf4-mcg-core-rhel8@sha256:9b207e17e531387e7c735589c6b4588bab0e584f313da5be0be437ca0d62c802 Configuring 9h $ Expected results: noobaa should be in Ready state Additional info: $ oc get noobaa -o yaml apiVersion: v1 items: - apiVersion: noobaa.io/v1alpha1 kind: NooBaa metadata: creationTimestamp: "2023-05-17T18:53:06Z" finalizers: - noobaa.io/graceful_finalizer generation: 2 labels: app: noobaa name: noobaa namespace: openshift-storage ownerReferences: - apiVersion: ocs.openshift.io/v1 blockOwnerDeletion: true controller: true kind: StorageCluster name: ocs-external-storagecluster uid: 75fb5e9b-a6ab-4741-8fd1-39c1621f234f resourceVersion: "349753" uid: 5679080f-75fa-4c1a-bf85-173bd1b21e0a . . . status: accounts: admin: secretRef: name: noobaa-admin namespace: openshift-storage actualImage: quay.io/rhceph-dev/odf4-mcg-core-rhel8@sha256:9b207e17e531387e7c735589c6b4588bab0e584f313da5be0be437ca0d62c802 conditions: - lastHeartbeatTime: "2023-05-17T18:53:07Z" lastTransitionTime: "2023-05-17T18:53:07Z" message: "InvalidRange: \n\tstatus code: 416, request id: tx000008deaed973d7f4fc2-006465a337-25a860-us-east, host id: " reason: TemporaryError status: "False" type: Available - lastHeartbeatTime: "2023-05-17T18:53:07Z" lastTransitionTime: "2023-05-17T18:53:07Z" message: "InvalidRange: \n\tstatus code: 416, request id: tx000008deaed973d7f4fc2-006465a337-25a860-us-east, host id: " reason: TemporaryError status: "True" type: Progressing - lastHeartbeatTime: "2023-05-17T18:53:07Z" lastTransitionTime: "2023-05-17T18:53:07Z" message: "InvalidRange: \n\tstatus code: 416, request id: tx000008deaed973d7f4fc2-006465a337-25a860-us-east, host id: " reason: TemporaryError status: "False" type: Degraded - lastHeartbeatTime: "2023-05-17T18:53:07Z" lastTransitionTime: "2023-05-17T18:53:07Z" message: "InvalidRange: \n\tstatus code: 416, request id: tx000008deaed973d7f4fc2-006465a337-25a860-us-east, host id: " reason: TemporaryError status: "False" type: Upgradeable - lastHeartbeatTime: "2023-05-17T18:53:07Z" lastTransitionTime: "2023-05-17T18:53:07Z" status: k8s type: KMS-Type - lastHeartbeatTime: "2023-05-17T18:53:07Z" lastTransitionTime: "2023-05-17T18:53:12Z" status: Sync type: KMS-Status observedGeneration: 2 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-20220913\n\tNooBaa Operator Version: 5.12.0\n" Jenkins job: https://url.corp.redhat.com/6346f44 must gather: https://url.corp.redhat.com/4685567