When noobaa-cli being run in crontab ilm_candidates and ilm_policies folder not getting created

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

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

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

Does this issue impact your ability to continue to work with the product?

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

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

Can this issue be reproduced from the UI?

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

Steps to Reproduce:

1. Put noobaa cli as crontab entry for running daily at midnight.

2. Ex: 0 0 * * * /usr/local/bin/noobaa-cli lifecycle
 

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

Actual results:
Below two directories not getting created.

*lifecycle_ilm_policies
lifecycle_ilm_candidates*
 

Expected results:

 We expect below two directories should be created for atleast expiration rules.:
*lifecycle_ilm_policies
lifecycle_ilm_candidates*
 

Logs collected and log location:

 [root@pr523-41 lifecycle]# ls -ltr
total 112
rw-r----. 1 root root 3804 May 6 12:26 lifecycle_run_1746527198679.json
rw-r----. 1 root root 3802 May 7 09:21 lifecycle_run_1746602519030.json
rw-r----. 1 root root 3802 May 8 07:19 lifecycle_run_1746681561009.json
rw-r----. 1 root root 3802 May 8 07:23 lifecycle_run_1746681790003.json
rw-r----. 1 root root 3802 May 8 07:59 lifecycle_run_1746683957646.json
rw-r----. 1 root root 3802 May 8 08:02 lifecycle_run_1746684161413.json

Additional info: