Env:

[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)

 

 

Description of problem - 
After running the lifecycle worker, it executed the policy successfully. However in the report it shows the num_objects_deleted" as 0 for "stats_acc"
This is for 4.18.3.
However in 4.19.0, this code block is not present in the report.

 

Example: Check the block in bold text.

[root@19may5231-31 lifecycle]# jq . lifecycle_run_1747733194338.json
{
  "running_host": "19may5231-31",
  "lifecycle_run_times":

{     "run_lifecycle_start_time": 1747733194338,     "list_buckets_start_time": 1747733194369,     "list_buckets_end_time": 1747733194369,     "list_buckets_took_ms": 0,     "process_buckets_start_time": 1747733194370,     "process_buckets_end_time": 1747733194499,     "process_buckets_took_ms": 129,     "run_lifecycle_end_time": 1747733194499,     "run_lifecycle_took_ms": 161   }

,
  "total_stats": {
    "stats_acc": {
      "num_objects_deleted": 0,
      "num_objects_delete_failed": 0,
      "objects_delete_errors": [],
      "num_mpu_aborted": 0,
      "num_mpu_abort_failed": 0,
      "mpu_abort_errors": []
    },
    "cur_op_stats":

{       "num_objects_deleted": 1,       "num_objects_delete_failed": 0,       "objects_delete_errors": []     }

  },
  "buckets_statuses": {
    "bucket7000": {
      "bucket_process_times":

{         "process_bucket_start_time": 1747733194370,         "process_bucket_end_time": 1747733194499,         "process_bucket_took_ms": 129       }

,
      "bucket_stats": {
        "stats_acc": {},
        "cur_op_stats":

{           "num_objects_deleted": 1,           "num_objects_delete_failed": 0,           "objects_delete_errors": []         }

      },
      "rules_statuses": {
        "expiration_days_1": {
          "rule_process_times":

{             "process_rule_start_time": 1747733194372,             "get_candidates_start_time": 1747733194374,             "get_candidates_end_time": 1747733194489,             "get_candidates_took_ms": 115,             "delete_multiple_objects_start_time": 1747733194489,             "delete_multiple_objects_end_time": 1747733194499,             "delete_multiple_objects_took_ms": 10,             "process_rule_end_time": 1747733194499,             "process_rule_took_ms": 127           }

,
          "rule_stats":

{             "num_objects_deleted": 1,             "num_objects_delete_failed": 0,             "objects_delete_errors": []           }

,
          "state":

{             "is_finished": true           }

        }
      },
      "state":

{         "num_processed_objects": 1,         "is_finished": true       }

    }
  },
  "state":

{     "is_finished": true   }

}

 

 

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

 

Steps to Reproduce:

1. Create a scale cluster with noobaa 5.18.3 and and apply a lifecycle policy.

2. Run the policy using "/usr/local/bin/noobaa-cli lifecycle --disable_runtime_validation" and see the report

3. In the report verify that all the object deleted count is proper