Description of problem (please be detailed as possible and provide log snippests): Discussed here: https://chat.google.com/room/AAAAREGEba8/J8CqmNwLOU8 In noobaa logs I see: message: cloud credentials secret "noobaa-aws-cloud-creds-secret" is not ready yet Jul-18 8:32:28.428 [Endpoint/13] [WARN] core.util.signature_utils:: Anonymous request: GET /geoserver/web/ { host: '18.118.62.167', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0', accept: '*/*', 'accept-encoding': 'gzip' } Jul-18 8:32:28.429 [Endpoint/13] [ERROR] core.endpoint.sts.sts_rest:: STS ERROR <?xml version="1.0" encoding="UTF-8"?><Error><Code>InternalFailure</Code><Message>The request processing has failed because of an unknown error, exception or failure.</Message><Resource>/geoserver/web/</Resource><RequestId>lk81duz0-cbs911-p0y</RequestId></Error> GET /geoserver/web/ {"host":"18.118.62.167","user-agent":"Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0","accept":"*/*","accept-encoding":"gzip"} Error: The request processing has failed because of an unknown error, exception or failure. at parse_request_body (/root/node_modules/noobaa-core/src/util/http_utils.js:275:15) at Object.read_and_parse_body (/root/node_modules/noobaa-core/src/util/http_utils.js:240:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async handle_request (/root/node_modules/noobaa-core/src/endpoint/sts/sts_rest.js:82:5) at async sts_rest (/root/node_modules/noobaa-core/src/endpoint/sts/sts_rest.js:40:9) Version of all relevant components (if applicable): ODF: 4.14.0-67 OCP: 4.14.0-0.nightly-2023-07-17-215017 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? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Yes Steps to Reproduce: 1. Install nightly OCP 4.14 and ODF on top of it 2. 3. Actual results: Installation is not finished as noobaa stuck in configuring - storageCluster is in progressing state as well. Expected results: Additional info: Logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-431ai3c33-a/j-431ai3c33-a_20230718T070024/logs/deployment_1689665559/j-431ai3c33-a/ocs_must_gather/
OCP fixed the issue, but no stable build yet. Moving to MODIFIED
AFAIK , OCP has fixed the issues, moving to ON QE
no issues seen in recent builds verified with 4.14.0-93, acceptance suite passed url: https://url.corp.redhat.com/6550bab logs: https://url.corp.redhat.com/7241d54
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