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.

Sign up for GitHub

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

Jump to bottom

Repo sync from RH registry fails with 404 #974

Closed
ipanova opened this issue Aug 17, 2022 · 1 comment · Fixed by #976
Closed

Repo sync from RH registry fails with 404 #974

ipanova opened this issue Aug 17, 2022 · 1 comment · Fixed by #976
Assignees
@ipanova
Labels
GalaxyNG Issue Katello prio-list

Comments

@ipanova
Copy link
Member

ipanova commented Aug 17, 2022 •
edited
Loading

Version
main but also older branches

To Reproduce

Steps to Reproduce:

  1. create a container repo
  2. create a container remote that would be syncing content from RH registry, for example rhosp-rhel8/openstack-aodh-api
  3. Hit the sync button
  4. And the task fails with 404 - Not found

Sync fails with:

404, message='Not Found', url=URL('https://registry.redhat.io/containers/content/dist/containers/rhel8/multiarch/containers/redhat-rhosp-rhel8-openstack-aodh-api/manifests/1/sha256:2881fb630130572a95d370ba801fec3340d6738c001abcab8d70bfc063ad9cd2?_auth_=exp=1659560550~hmac=caae5ac4009b16a60c419da47fca4713362f5a3c24f6f6d6f288476a31f96161')

Additional context
https://bugzilla.redhat.com/show_bug.cgi?id=2115970
ipanova added a commit to ipanova/pulp_container that referenced this issue Aug 17, 2022
@ipanova
Fixed 404 during sync from registry.redhat.io
5417c7f 
Whenever a token expires a new token is requested.
The 401 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 unsuppotrted since july 2022)
because of absense of the accept headers.

closes pulp#974
@ipanova ipanova self-assigned this Aug 17, 2022
ipanova added a commit to ipanova/pulp_container that referenced this issue Aug 17, 2022
@ipanova
Fixed 404 during sync from registry.redhat.io
cc9db0c 
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 unsuppotrted since july 2022)
because of absense of the accept headers.

closes pulp#974
@ipanova ipanova mentioned this issue Aug 17, 2022
Merged
ipanova added a commit to ipanova/pulp_container that referenced this issue Aug 17, 2022
@ipanova
Fixed 404 during sync from registry.redhat.io
133cc0d 
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 unsuppotrted since july 2022)
because of absense of the accept headers.

closes pulp#974
ipanova added a commit to ipanova/pulp_container that referenced this issue Aug 17, 2022
@ipanova
Fixed 404 during sync from registry.redhat.io
0a0e005 
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 pulp#974
ipanova added a commit to ipanova/pulp_container that referenced this issue Aug 17, 2022
@ipanova
Fixed 404 during sync from registry.redhat.io
bdbc517 
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 pulp#974
ipanova added a commit to ipanova/pulp_container that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
8e71db0 
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 pulp#974
ipanova added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
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
patchback bot pushed a commit that referenced this issue Aug 22, 2022
@ipanova @patchback
Fixed an HTTP 404 response during sync from registry.redhat.io.
c139f67 
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)
@patchback patchback bot mentioned this issue Aug 22, 2022
Merged
patchback bot pushed a commit that referenced this issue Aug 22, 2022
@ipanova @patchback
Fixed an HTTP 404 response during sync from registry.redhat.io.
8bbc383 
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)
@patchback patchback bot mentioned this issue Aug 22, 2022
Merged
patchback bot pushed a commit that referenced this issue Aug 22, 2022
@ipanova @patchback
Fixed an HTTP 404 response during sync from registry.redhat.io.
b14799a 
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)
@patchback patchback bot mentioned this issue Aug 22, 2022
Merged
patchback bot pushed a commit that referenced this issue Aug 22, 2022
@ipanova @patchback
Fixed an HTTP 404 response during sync from registry.redhat.io.
1be5c98 
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)
@patchback patchback bot mentioned this issue Aug 22, 2022
Merged
patchback bot pushed a commit that referenced this issue Aug 22, 2022
@ipanova @patchback
Fixed an HTTP 404 response during sync from registry.redhat.io.
b96e0b2 
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)
@patchback patchback bot mentioned this issue Aug 22, 2022
Merged
patchback bot pushed a commit that referenced this issue Aug 22, 2022
@ipanova @patchback
Fixed an HTTP 404 response during sync from registry.redhat.io.
9c767c9 
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)
@patchback patchback bot mentioned this issue Aug 22, 2022
Merged
ipanova added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
5bdd4d9 
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 added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
3865e77 
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 added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
9c4efe8 
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 added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
fcab889 
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 added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
bd1016c 
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 added a commit that referenced this issue Aug 22, 2022
@ipanova
Fixed an HTTP 404 response during sync from registry.redhat.io.
38ec0ab 
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)
@pulpbot
Copy link
Member

pulpbot commented Mar 2, 2023

https://bugzilla.redhat.com/show_bug.cgi?id=2166749

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ipanova ipanova

Labels
GalaxyNG Issue Katello prio-list
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed 404 during sync from registry.redhat.io ipanova/pulp_container
2 participants
@ipanova @pulpbot