The task result is inconsistent with the actual garbage collection situation

[laoyigrace]

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:
Currently, there are many image layers in Harbor that need to be recycled. When the artifact garbage collection (GC) task is executed, the JobService service is abnormally restarted. The task result shows that 0 blobs are released and 0 storage space is released, while actually many blobs have been deleted. The task result is inconsistent with the actual garbage collection situation.

Steps to reproduce the problem:

1. Ensure that there are many image layers in Harbor that need to be cleaned up.
2. Execute the image cleanup task.
3. Abnormally restart the jobservice service.
4. The task result shows 0 blobs and 0 storage released, although the blobs in the S3 storage and database have actually decreased.

Versions:
Please specify the versions of following systems.

• harbor version: [2.11.0]
• docker engine version: [y.y.y]
• docker-compose version: [z.z.z]

Additional context:

• Harbor config files: You can get them by packaging harbor.yml and files in the same directory, including subdirectory.
• Log files: You can get them by package the /var/log/harbor/ .