Description of problem (please be detailed as possible and provide log
snippests):
ODF installation with in-transit encryption fails on Provider cluster. In noobaa-operator logs is repeated message:

time="2024-08-19T21:35:24Z" level=info msg="✅ Exists: \"ocs-storagecluster-cephcluster\"\n"
time="2024-08-19T21:35:24Z" level=info msg="Create event detected for rook-ceph-client-2daff4e335b263572c8d177cfc4dff75 (openshift-storage), queuing Reconcile"
time="2024-08-19T21:35:24Z" level=info msg="will reconcile these namespaceStores: []"
time="2024-08-19T21:35:24Z" level=info msg="Create event detected for ocs-client-operator-status-reporter-dockercfg-fq455 (openshift-storage), queuing Reconcile"
time="2024-08-19T21:35:24Z" level=info msg="checking which namespaceStores to reconcile. mapping secret openshift-storage/ocs-client-operator-status-reporter-dockercfg-fq455 to namespaceStores"
time="2024-08-19T21:35:24Z" level=info msg="✅ Exists: NooBaa \"noobaa\"\n"
time="2024-08-19T21:35:24Z" level=info msg="✅ Exists: Service \"noobaa-mgmt\"\n"
time="2024-08-19T21:35:24Z" level=info msg="❌ Not Found: Secret \"noobaa-operator\"\n"
time="2024-08-19T21:35:24Z" level=error msg="Could not connect to system Connect(): SecretOp not found"
time="2024-08-19T21:35:24Z" level=info msg="ReconcileObject: Done - unchanged Role noobaa-db " sys=openshift-storage/noobaa
time="2024-08-19T21:35:24Z" level=info msg="will reconcile these namespaceStores: []"
time="2024-08-19T21:35:24Z" level=info msg="Create event detected for onboarding-ticket-key (openshift-storage), queuing Reconcile"
time="2024-08-19T21:35:24Z" level=info msg="checking which namespaceStores to reconcile. mapping secret openshift-storage/onboarding-ticket-key to namespaceStores"
time="2024-08-19T21:35:24Z" level=info msg="Create event detected for rook-ceph-mds-ocs-storagecluster-cephfilesystem-a-keyring (openshift-storage), queuing Reconcile"

The secret noobaa-operator does not exist in openshift-storage namespace:
$ oc get secret -n openshift-storage | grep noobaa-operator
noobaa-operator-service-cert                                                                      kubernetes.io/tls         3      5h38m


Version of all relevant components (if applicable):
ODF 4.17.0-78
OCP 4.17.0-ec.3

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

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?
1/1

Steps to Reproduce:
1. Deploy ODF with in-transit encryption and deployment mode: provider
2. Create storage cluster
2. Check status of NooBaa Operator

Actual results:
NooBaa operator is not installed sucessfully and fails with:
ComponentUnhealthy
installing: waiting for deployment noobaa-operator to become ready: deployment "noobaa-operator" not available: Deployment does not have minimum availability.


Expected results:
NooBaa operator is installed correctly.

Additional info:
OCP and OCS must gather logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/ibm-baremetal2/ibm-baremetal2_20240819T032525/logs/testcases_1724103587/ibm-baremetal2/