noobaa version:noobaa-core-5.18.4-20250527.el8.x86_64

Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:

I was performing the following scenario 10 buckets in total, 2 with versioning enabled, 1 with versioning suspended and the other 7 without versioning all with 1k files of different sizes, the following policies were applied to these buckets
{
  "Rules": [
    {
      "ID": "expiration_days_1_with_prefix_obj",
      "Status": "Enabled",
      "Filter":

{         "Prefix": "obj",         "ObjectSizeGreaterThan": 0,         "ObjectSizeLessThan": 1048577       }

,
      "Expiration":

{         "Days": 1       }

    },
    {
      "ID": "expiration_days_1_with_prefix_50M",
      "Status": "Enabled",
      "Filter":

{         "Prefix": "50M",         "ObjectSizeGreaterThan": 1048577,         "ObjectSizeLessThan": 52428801       }

,
      "Expiration":

{         "Days": 1       }

    },
    {
      "ID": "expiration_days_1_with_prefix_100M",
      "Status": "Enabled",
      "Filter":

{         "Prefix": "100M",         "ObjectSizeGreaterThan": 52428801,         "ObjectSizeLessThan": 104857601       }

,
      "Expiration":

{         "Days": 1       }

    }
  ]
}

Of which only the first was going to be carried out (all these policies were previously tested) at the time of execution of the policy the files that complied with the policy were eliminated but only from the buckets without versioning

Some more tests were performed using the following policy in a new bucket with versioning enabled, which is quite similar to the previous one, and a few files were created several times. In this situation, it was observed that the policy was executed, and the files were deleted.

{
    "Rules": [
        {
            "ID": "expiration_date_with_prefix_obj",
            "Status": "Enabled",
            "Filter":

{                 "Prefix": "obj"             }

,
            "Expiration":

{                 "Date": "2025-03-05"             }

        }
    ]
}

I add the following logs from the node running BLC in my cluster: the lifecylce_run and the noobaa.log
the run started at 09:05:02
The errors err_code":"EPERM","err_message":"Operation not permitted" were observed in the lifecycle run log in the buckets with versioning enabled, bucket1 and bucket2.

lifecycle_run_1749477902508.json

[^noobaa.log]

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

yes

 

 

 

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

yes

 

 

 

 

 

Steps to Reproduce:

1. create a bucket with versioning enable

2. create 1k files with different sizes

3. apply the policy

 

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

the run started at 09:05:02

Actual results:

undeleted files 

 

Expected results:

deleted files

Logs collected and log location:

 

Additional info: