-
Notifications
You must be signed in to change notification settings - Fork 45
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
Pull-through caching may fail on a non-localfilesystem storage backend #1493
Comments
Intermittent failures in the CI were caused by
|
I believe we're seeing this same behavior with NFS-backed storage, which is probably related to this. I'll be upgrading Docker on our K8s nodes this week so if we stop seeing 500's that would confirm it. |
Same happens on
|
The issue might lie here:
The highlighted code part is evaluated to We should be able to handle a scenario where an artifact is stored on the object storage but we are in the process of returning the content initialized during the pull through caching.
|
This commit removes the check against `REDIRECT_TO_OBJECT_STORAGE` from the Registry handler that caused Pulp to stream content only when a user opted for it. Now, the content is always streamed from content-app when using non-local filesystem storage. closes pulp#1493
This commit removes the check against `REDIRECT_TO_OBJECT_STORAGE` from the Registry handler that caused Pulp to stream content only when a user opted for it. Now, the content is always streamed from content-app when using non-local filesystem storage. closes pulp#1493
Steps to reproduce:
podman pull
to trigger the pull-through cachingCI logs (pulp/S3):
Traceback:
The text was updated successfully, but these errors were encountered: