Description of problem (please be detailed as possible and provide log snippets): when the cloud credentials operator can't or fails to provide credentials (e.g.: the CCO is in manual mode), the creation of noobaa is stuck, waiting for the CCO to create the credentials secret Version of all relevant components (if applicable): 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? yes. creating the default BS manually 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? yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. install ODF in manual mode 2. 3. Actual results: noobaa installation is stuck pending on the credentials secret Expected results: noobaa should fallback to a pv pool BS after a timeout. A proper alert should be generated, notifying the user of the failure to create a default BS of the intended type, and the creation of a pv-pool BS Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6832