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

Unexpected behavior for proxy cache #17933

Closed
AllForNothing opened this issue Dec 7, 2022 · 1 comment · Fixed by #17936
Closed

Unexpected behavior for proxy cache #17933

AllForNothing opened this issue Dec 7, 2022 · 1 comment · Fixed by #17936
Assignees

Comments

@AllForNothing
Copy link
Contributor

A wrong message is reported in core.log when pulling a cached image from a proxy cache project:
2022-12-06T10:05:58Z [WARNING] [/server/middleware/repoproxy/proxy.go:197]: Artifact: proxy_dockerhub/library/redis:latest, digest: is not found in proxy cache, fetch it from remote repo

Steps to reproduce:

 - Create a registry  for Dockerhub with username and password
 - Create a private proxy cache for this registry named dockerhub_proxy
 - Pull an image with username and password without project name
 - Verify the image could pull and the image is cached in proxy cache project after 15 minutes
 - Pull the image again then the wrong message is reported in core.log

version: 2.7

@stonezdj
Copy link
Contributor

stonezdj commented Dec 7, 2022

It is inaccurate log information, actually it just head the manifest in the remote server to check if the digest change, it doesn't pull the content from remote server.

stonezdj pushed a commit to stonezdj/harbor that referenced this issue Dec 7, 2022
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Dec 7, 2022
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Dec 7, 2022
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Dec 7, 2022
stonezdj added a commit that referenced this issue Dec 8, 2022
fixes #17933

Signed-off-by: stonezdj <[email protected]>

Signed-off-by: stonezdj <[email protected]>
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Dec 8, 2022
stonezdj added a commit that referenced this issue Dec 9, 2022
Update the log information in proxy cache

  fixes #17933

Signed-off-by: stonezdj <[email protected]>

Signed-off-by: stonezdj <[email protected]>
OrlinVasilev pushed a commit to OrlinVasilev/harbor that referenced this issue Dec 12, 2022
tpoxa pushed a commit to container-registry/harbor that referenced this issue Feb 8, 2023
fixes goharbor#17933

Signed-off-by: stonezdj <[email protected]>

Signed-off-by: stonezdj <[email protected]>
Signed-off-by: Maksym <[email protected]>
mcsage pushed a commit to mcsage/harbor that referenced this issue Feb 16, 2023
fixes goharbor#17933

Signed-off-by: stonezdj <[email protected]>

Signed-off-by: stonezdj <[email protected]>
Signed-off-by: Stephan Hohn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants