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:

noncurrent version expiration when newer noncurrent versions not working in NooBaa's lifecycle 

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

IBM Power UPI

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

Internal-Attached (LSO)

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

OCP:  4.19.0-rc.3
ODF:  4.19.0-76.stable

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

yes

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

No

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

100%

Can this issue be reproduced from the UI?

yes

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

Steps to Reproduce:

1. Create an MCG bucket with versioning enabled
2. Set onto the bucket a lifecycle configuration with the NoncurrentVersionExpiration rule with NoncurrentDays set to 5 and NewerNoncurrentVersions set to 7
3. Upload 11 versions for the same object
4. By modifying the noobaa-db, set the creation date of each non-current version to be one day earlier than that of it's successor. This will map the list of non-current versions to a linear list of NoncurrentDays. From newest to oldest: [1, 2, 3...10]
5. Wait for versions to expire

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

21-05-2025:11:30 AM IST

Actual results:

noncurrent versions are not removed from MCG bucket.

Expected results:

noncurrent versions would remove from MCG bucket.

Logs collected and log location:

must-gather.tar.gz

Additional info: