Krishnan Parthasarathi 383489d5d9
Handle zero versions qualified for expiration (#19301)
When objects have more versions than their ILM policy expects to retain
via NewerNoncurrentVersions, but they don't qualify for expiry due to
NoncurrentDays are configured in that rule. 

In this case, applyNewerNoncurrentVersionsLimit method was enqueuing empty 
tasks, which lead to a panic (panic: runtime error: index out of range [0] with
length 0) in newerNoncurrentTask.OpHash method, which assumes the task
to contain at least one version to expire.
2024-03-19 20:10:58 -07:00
..
2024-01-17 23:03:17 -08:00
2024-01-17 23:03:17 -08:00
2023-09-04 12:57:37 -07:00
2024-01-17 23:03:17 -08:00
2023-12-20 20:13:40 -08:00
2024-03-10 01:15:15 -08:00
2024-01-17 23:03:17 -08:00