You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior and actual behavior:
Expected:Garbage collection of untaged and cosigned artifacts should not fail, and artifact and signature should be collected together
Actual:Garbage collection untaged and is cosign signed artifact fail
Steps to reproduce the problem:
push untaged artifact to harbor
Use cosign sign artifact
3. Check Allow garbage collection on untagged artifacts and trigger GC
Versions:
harbor version: v2.5.0-abd85284
Additional context:
GC error log
2022-02-25T07:11:05Z [INFO] [/jobservice/job/impl/gc/garbage_collection.go:145]: Garbage Collection parameters: [delete_untagged: true, dry_run: false, time_window: 2]
2022-02-25T07:11:05Z [INFO] [/jobservice/job/impl/gc/garbage_collection.go:155]: start to run gc in job.
2022-02-25T07:11:05Z [INFO] [/jobservice/job/impl/gc/garbage_collection.go:418]: start to delete untagged artifact (no actually deletion for dry-run mode)
The text was updated successfully, but these errors were encountered:
…tary
Make func defaultMgr() public
Set DefaultCfgManager to RestCfgManager and Load it in the jobservice main
config.WithNotary call DefaultMgr(), it wil get the RestCfgManager
Fixesgoharbor#16418
Signed-off-by: stonezdj <stonezdj@gmail.com>
…tary
Make func defaultMgr() public
Set DefaultCfgManager to RestCfgManager and Load it in the jobservice main
config.WithNotary call DefaultMgr(), it wil get the RestCfgManager
Fixesgoharbor#16418
Signed-off-by: stonezdj <stonezdj@gmail.com>
Expected behavior and actual behavior:
Expected:Garbage collection of untaged and cosigned artifacts should not fail, and artifact and signature should be collected together
Actual:Garbage collection untaged and is cosign signed artifact fail
Steps to reproduce the problem:
3. Check Allow garbage collection on untagged artifacts and trigger GC
Versions:
Additional context:
GC error log
The text was updated successfully, but these errors were encountered: