Description of problem - 
Not able to start S3 service after deploying the rpms on scale cluster

The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
Scale 

The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):
Standalone noobaa

The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable): ODF

Does this issue impact your ability to continue to work with the product?
This is blocking the test efforts

Is there any workaround available to the best of your knowledge?

Not available

Can this issue be reproduced? If so, please provide the hit rate

Yes. Consistently

Can this issue be reproduced from the UI?

N/A

If this is a regression, please provide more details to justify this:

This was working in previous build with date 01/17.

Steps to Reproduce:

1. Install rpms on a scale cluster.

2. Start the s3 service

3. Service not able to start

[root@buildval-21 ~]# rpm -qa | grep noobaa
noobaa-core-5.21.0-20260211.el9.x86_64

[root@buildval-21 ~]# systemctl status noobaa
● noobaa.service - The NooBaa service.
     Loaded: loaded (/usr/lib/systemd/system/noobaa.service; disabled; preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2026-02-12 06:31:23 CET; 700ms ago
    Process: 486925 ExecStart=/usr/local/noobaa-core/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js (code=exited, status=1/FAILURE)
   Main PID: 486925 (code=exited, status=1/FAILURE)
        CPU: 2.572s

Feb 12 06:31:23 buildval-21 systemd[1]: noobaa.service: Failed with result 'exit-code'.
Feb 12 06:31:23 buildval-21 systemd[1]: noobaa.service: Consumed 2.572s CPU time.

Seeing this error in noobaa.log

Feb 12 00:00:03 buildval-21 node[4055824]: [noobaa-cli/4055824] ^{[[33m [WARN]}[[39m core.sdk.config_fs:: get_config_data: with config_file_path /mnt/cesSharedRoot/ces/s3-config/system.json got an error [Error: No such file or directory] { code: ^{[[32m'ENOENT'}[[39m, context: ^{[[32m'Readfile _path=/mnt/cesSharedRoot/ces/s3-config/system.json '}[[39m }
Feb 12 00:00:03 buildval-21 node[4055824]: [noobaa-cli/4055824] ^[[31m[ERROR][[39m core.manage_nsfs.nc_lifecycle:: throw_if_noobaa_not_active: system.json is missing

So eventually figured out that system.json is missing under s3-config directory

[root@buildval-21 ~]# ls -la /mnt/cesSharedRoot/ces/s3-config/
total 12
drwxr-xr-x. 7 root root 4096 Feb 12 06:29 .
drwxr-xr-x. 5 root root 8192 Feb 12 06:30 ..
drwx------. 2 root root 4096 Feb 12 06:29 access_keys
drwx------. 2 root root 4096 Feb 12 06:29 accounts_by_name
drwx------. 2 root root 4096 Feb 12 06:29 buckets
rwx-----. 1 root root 1065 Feb 12 06:29 config.json
drwx------. 2 root root 4096 Feb 12 06:29 connections
drwx------. 2 root root 4096 Feb 12 06:29 identities

The exact date and time when the issue was observed, including timezone details:

Actual results:

Expected results:

Logs collected and log location:

Additional info: