Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

harbor replication 401 #21220

Open
mengjinmm opened this issue Nov 20, 2024 · 0 comments
Open

harbor replication 401 #21220

mengjinmm opened this issue Nov 20, 2024 · 0 comments

Comments

@mengjinmm
Copy link

mengjinmm commented Nov 20, 2024

If two harbors share one set of NFS, Redis and PG, the image replication task will fail. The logs are as follows:

2024-11-19T09:27:32Z [INFO] [/controller/replication/transfer/image/transfer.go:210]: copying echery/ipark-safety:202310251442(source registry) to echery/ipark-safety:202310251442(destination registry)...
2024-11-19T09:27:32Z [INFO] [/controller/replication/transfer/image/transfer.go:467]: pulling the manifest of artifact echery/ipark-safety:202310251442 ...
2024-11-19T09:27:32Z [INFO] [/controller/replication/transfer/image/transfer.go:473]: the manifest of artifact echery/ipark-safety:202310251442 pulled
2024-11-19T09:27:32Z [ERROR] [/controller/replication/transfer/image/transfer.go:481]: failed to check the existence of the manifest of artifact echery/ipark-safety:202310251442 on the destination registry: http status code: 401, body: 
2024-11-19T09:27:32Z [ERROR] [/controller/replication/transfer/image/transfer.go:194]: http status code: 401, body: 
2024-11-19T09:27:32Z [ERROR] [/controller/replication/transfer/image/transfer.go:200]: got error during the whole transfer period, mark the job failure
  • harbor version: v2.6.2-b351d276
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant