Project

Profile

Help

Issue #7620

pulpcore registry api doesn't like Accept headers when syncing from pulp

Added by jsherril@redhat.com 2 months ago. Updated about 1 month ago.

Status:
MODIFIED
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 85
Quarter:

Description

When i have a pulp3 installation with pulp_container 2.0.1 hosting a container repository and i setup a 2nd pulp3 server and try to sync from it, i get an error:

{"errors":[{"code":"UNSUPPORTED","message":"Could not satisfy the request Accept header.","detail":{}}]

It seems that pulp3 doesn't like the Accept header that the other pulp3 server is requesting:

here's the accept header from the syncing pulpcore server:

"application/vnd.docker.distribution.manifest.v2+json,application/vnd.docker.distribution.manifest.list.v2+json,application/vnd.oci.image.index.v1+json,application/vnd.oci.image.manifest.v1+json"

if i delete that header on the request (in our shim layer), it goes through fine.

Associated revisions

Revision 970e2cfd View on GitHub
Added by ipanova@redhat.com about 1 month ago

Fixed Renderer to handle properly Manifest and Blob responses.

closes #7620 https://pulp.plan.io/issues/7620

History

#1 Updated by jsherril@redhat.com 2 months ago

and to clarify, this is happening when the blobs are being fetched. It appears the manifests are fetched with no issue

#2 Updated by ipanova@redhat.com 2 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 82

#3 Updated by ipanova@redhat.com 2 months ago

(07:50:54 PM) ipanova: quick google fu showed that we need to write a custom renderer https://stackoverflow.com/questions/30903951/django-doesnt-parse-a-custom-http-accept-header
(07:51:20 PM) ipanova: https://github.com/pulp/pulp_container/blob/47781dbab4b852542303bee5980c41030aa03d9b/pulp_container/app/registry_api.py#L111
(07:51:29 PM) ipanova: we have it written for the manifest but not for blobs

#4 Updated by rchan 2 months ago

  • Sprint changed from Sprint 82 to Sprint 83

#5 Updated by ipanova@redhat.com about 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com

#6 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 83 to Sprint 84

#7 Updated by pulpbot about 1 month ago

  • Status changed from ASSIGNED to POST

#8 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 84 to Sprint 85

#9 Updated by ipanova@redhat.com about 1 month ago

  • Status changed from POST to MODIFIED

Please register to edit this issue

Also available in: Atom PDF