Description of problem - 

After running the lifecycle worker, it executed the policy successfully. However ILM policies and candidates directories are not created after that.

 

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

[root@19may5231-31 lifecycle]# rpm -qa | grep noobaa
noobaa-core-5.18.3-20250514.el9.x86_64
[root@19may5231-31 lifecycle]# mmdiag
Current GPFS build: "5.2.3.1".
Built on May 19 2025 at 17:06:32

[root@19may5231-31 lifecycle]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.4 (Plow)

 

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

 

Steps to Reproduce:

1. Create a scale cluster and apply a bucket lifecycle policy
Policy
[root@fa-akarattu-mgmt-host policies]# aws-test s3api get-bucket-lifecycle-configuration --bucket bucket7000
{
    "Rules": [
        {
            "Expiration":

{                 "Date": "2025-05-05T00:00:00+00:00"             }

,
            "ID": "expiration_days_1",
            "Filter":

{                 "Prefix": "file",                 "ObjectSizeGreaterThan": 0,                 "ObjectSizeLessThan": 500             }

,
            "Status": "Enabled"
        }
    ]
}

2. Execute the policy and make sure that it deleted the objects as intended. --> Done

3. Now verify the default directory "/var/log/noobaa/lifecycle" and make sure that corresponding json file as well as directories appear inside the default directory

[root@19may5231-31 lifecycle]# pwd
/var/log/noobaa/lifecycle
[root@19may5231-31 lifecycle]# ls -l
total 4
rw-r----. 1 root root 1584 May 20 11:26 lifecycle_run_1747733194338.json

 

Currently ILM directories are missing in 4.18.3. 
I see that they are present in 4.19.0.