Steps to Reproduce:

1.noobaa-cli diagnose health --lifecycle
"response": {
    "code": "HealthStatus",
    "message": "Health status retrieved successfully",
    "reply": {
      "service_name": "noobaa",
       .....
      "lifecycle": {
          "latest_lifecycle_run_stats":

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

,
          "lastest_lifecycle_run_errors": [
            "Lifecycle worker reached timeout - configured timeout is 1 ms"
          ],
          "latest_lifecycle_run_times":

{             "run_lifecycle_start_time": 1742739265387,             "list_buckets_start_time": 1742739265387,             "list_buckets_end_time": 1742739265387,             "list_buckets_took_ms": 0,             "process_buckets_start_time": 1742739265387,             "run_lifecycle_end_time": 1742739265388,             "run_lifecycle_took_ms": 1           }

        }
...
}

2.

3.

 

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

 

Actual results:

 

          "latest_lifecycle_run_stats":

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

,
          "lastest_lifecycle_run_errors": [
            "Lifecycle worker reached timeout - configured timeout is 1 ms"
          ],

Expected results:

It should be bucket wise not with the object wise

If for particular bucket lifecycle failed to delete then it should be notified

Logs collected and log location:

 

Additional info: