getting 404 response for s3 protocol nodes when doing GET bucket command

[PravinRanjan10]

Environment info

• NooBaa Version: 5.18.0

Actual behavior

Expected behavior

Steps to reproduce

1. I'm trying to run a multi-protocol workload with SMB, NFS and S3 protocol services using LDX.  IO will consists of 5k concurrent connections (15k in total) per protocol which are spread across 10 CES protocol node.
   LDX is reporting errors while doing GET_BUCKET commands after ~7 minutes into the run - it gets 404 response code. For debugging purposes the workload stops right after the first 404.

More information - Screenshots / Logs / Other output

zgrep Error  /var/log/noobaa.log-20250320.gz
Mar 19 23:31:15 spectre15 [2825045]: 2025-03-19 23:31:15.409362 [PID-2825045/TID-2825045] [L1] FS::FSWorker::OnError: Mkdir _path=/gpfs/spectrefs_prt/buckets_1/bucket373/.versions _mode=504  error.Message()=File exists

Mar 19 23:31:31 spectre15 [2825007]: [nsfs/2825007] [ERROR] core.endpoint.s3.s3_rest:: S3 ERROR NoSuchKeyThe specified key does not exist./bucket123m8guth4d-91p9c-17ot GET /bucket123 {"host":"10.18.56.33","user-agent":"VirtualInstruments","accept":"text/xml","accept-encoding":"identity","accept-language":"en","date":"Thu, 20 Mar 2025 04:31:31 GMT","authorization":"AWS B6AJCAyDXHZyyV9Iuvrc:YFv1uCgNkNDOFdMqiqEveKaEYlk="} Error: No such file or directory - context: Stat _path=/gpfs/spectrefs_prt/buckets_1/bucket123/object_112352.mpeg

[romayalon]

Hey @PravinRanjan10, thanks for opening this issue
Please provide NooBaa configuration and full NooBaa logs.
For efficient debugging process, please check the bugs reporting required information - https://github.com/noobaa/noobaa-core/blob/master/docs/NooBaaNonContainerized/Troubleshooting.md#bugs-reporting

[romayalon]

@PravinRanjan10 BTW, Could you also move this bug to Jira?