Purge command doesn't purge all images

[balcsida]

Describe the bug We have a registry with more than 200 images. I've run the following command: az acr run --cmd "acr purge --filter 'imagename:.*' --ago 730d --dry-run" --registry registryname /dev/null

Queued a run with ID: cbp
Waiting for an agent...
2024/05/08 12:48:16 Alias support enabled for version >= 1.1.0, please see https://aka.ms/acr/tasks/task-aliases for more information.
2024/05/08 12:48:16 Creating Docker network: acb_default_network, driver: 'bridge'
2024/05/08 12:48:17 Successfully set up Docker network: acb_default_network
2024/05/08 12:48:17 Setting up Docker configuration...
2024/05/08 12:48:17 Successfully set up Docker configuration
2024/05/08 12:48:17 Logging in to registry: registryname.azurecr.io

2024/05/08 12:48:28 Successfully logged into registryname.azurecr.io
2024/05/08 12:48:28 Executing step ID: acb_step_0. Timeout(sec): 600, Working directory: '', Network: 'acb_default_network'
2024/05/08 12:48:28 Launching container with name: acb_step_0
DRY RUN: The following output shows what WOULD be deleted if the purge command was executed. Nothing is deleted.
Tags for this repository would be deleted: imagename
registryname.azurecr.io/imagename:2.0.4
registryname.azurecr.io/imagename:1.0.191
registryname.azurecr.io/imagename:1.0.190
registryname.azurecr.io/imagename:1.0.189
registryname.azurecr.io/imagename:1.0.182
registryname.azurecr.io/imagename:1.0.174
registryname.azurecr.io/imagename:1.0.171
registryname.azurecr.io/imagename:1.0.170
registryname.azurecr.io/imagename:1.0.169
registryname.azurecr.io/imagename:1.0.168
registryname.azurecr.io/imagename:1.0.162
registryname.azurecr.io/imagename:1.0.161
registryname.azurecr.io/imagename:1.0.160
registryname.azurecr.io/imagename:1.0.159
registryname.azurecr.io/imagename:1.0.157
registryname.azurecr.io/imagename:1.0.154
registryname.azurecr.io/imagename:1.0.153
registryname.azurecr.io/imagename:1.0.152
registryname.azurecr.io/imagename:1.0.151
registryname.azurecr.io/imagename:1.0.150
registryname.azurecr.io/imagename:1.0.149
registryname.azurecr.io/imagename:1.0.148
registryname.azurecr.io/imagename:1.0.129
registryname.azurecr.io/imagename:1.0.128
registryname.azurecr.io/imagename:1.0.127
registryname.azurecr.io/imagename:1.0.126
registryname.azurecr.io/imagename:1.0.125
registryname.azurecr.io/imagename:1.0.124
registryname.azurecr.io/imagename:1.0.122
registryname.azurecr.io/imagename:1.0.121

Number of tags to be deleted: 30
Number of manifests to be deleted: 0
2024/05/08 12:48:33 Successfully executed container: acb_step_0
2024/05/08 12:48:33 Step ID: acb_step_0 marked as successful (elapsed time in seconds: 5.673937)

Run ID: cbp was successful after 18s

However, we have images older than that, like registryname.azurecr.io/imagename:1.0.120 but those are not marked for deletion. For this case, it should have been 100+

To Reproduce Steps to reproduce the behavior:

1. (I think) Have a lot of images in your registry, with a lot of old ones
2. az acr run --cmd "acr purge --filter 'imagename:.*' --ago 730d --dry-run" --registry registryname /dev/null
3. "Number of tags to be deleted: 30"

Expected behavior Should list all the to be delete

Screenshots

Any relevant environment information

Additional context