[PR #976/16e104ff backport][2.13] Fixed 404 during sync from registry.redhat.io #1002
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![patchback[bot]](https://avatars.githubusercontent.com/in/21488?s=60&v=4){kind=small}
Whenever a token expires a new token is requested. The 404 sync problem was triggered because the accept headers that were passed originally with the expired token were not passed to the re-newed token. As a result the registry was redirecting to the wrong schema version (schema1, which is unsupported since july 2022 https://access.redhat.com/articles/6138332) because of absense of the accept headers. closes #974 (cherry picked from commit 16e104f)
ipanova
approved these changes
Aug 22, 2022
fao89
deleted the
patchback/backports/2.13/16e104ff0b2bf1ca86003a875b13bf1bbdc1c792/pr-976
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #976 as merged into main (16e104f).
Whenever a token expires a new token is requested.
The 404 sync problem was triggered because the accept headers that
were passed originally with the expired token were not passed to the
re-newed token. As a result the registry was redirecting to the wrong
schema version (schema1, which is unsupported since july 2022
https://access.redhat.com/articles/6138332) because of absense of the
accept headers.
closes #974