goharbor/harbor

Event based replication failed with registry.gitlab.com

Open

#21,066 建立於 2024年10月20日

在 GitHub 查看
 (3 留言) (2 反應) (0 負責人)Go (28,490 star) (5,235 fork)batch import
area/replicationhelp wantedkind/bugnever-stale

描述

Steps to reproduce

  1. Setup a event based replication from Harbor to registry.gitlab.com, which support delete remote resource when local resource is deleted. the token in registry.gitlab.com should have full access to the registry(read_registry, write_registry)

  2. Push a new image to Harbor project

  3. Verify the new image is replicated to the registry.gitlab.com

  4. Delete the new image in the Harbor, it should trigger a replication job to delete the image from registry.gitlab.com, but the replication failed with following error message:

error message:

2024-10-20T04:55:39Z [INFO] [/controller/replication/transfer/image/transfer.go:140]: client for source registry [type: harbor, URL: https://core:8443, insecure: false] created
2024-10-20T04:55:39Z [INFO] [/controller/replication/transfer/image/transfer.go:150]: client for destination registry [type: gitlab, URL: https://registry.gitlab.com, insecure: true] created
2024-10-20T04:55:41Z [ERROR] [/controller/replication/transfer/image/transfer.go:533]: failed to delete the manifest of artifact harbor424542/harbor-ci/test_push_repli:v1.1.0 on the destination registry: http status code: 401, body: {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"harbor424542/harbor-ci/test_push_repli","ProjectPath":"","Action":"delete"}]}]}

貢獻者指南

技術棧
gorest api
領域
backendapi
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
GoDocker Registry APIGitLab token permissions
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the 401 Unauthorized error when deleting manifests on registry.gitlab.com. The error occurs in transfer.go at line 533. Check if the GitLab registry client is using the correct token scope for delete operations. The destination registry token must include delete permission (write registry). Review how the token is obtained and passed to the client. Also verify the endpont URL and authentication headers for delete requests. Look at existing integrations with GitLab registry in the codebase.