https://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-09-29T16:52:56ZPulpContainer Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=630792020-09-29T16:52:56Zjsherril@redhat.comjsherril@redhat.com
<ul></ul><p>and to clarify, this is happening when the blobs are being fetched. It appears the manifests are fetched with no issue</p> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=631582020-09-30T17:46:38Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint</strong> set to <i>Sprint 82</i></li></ul> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=631592020-09-30T18:04:11Zipanova@redhat.comipanova@redhat.com
<ul></ul><pre><code>(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
</code></pre> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=632272020-10-02T16:03:47Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 82</i> to <i>Sprint 83</i></li></ul> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=634252020-10-08T14:40:52Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>ipanova@redhat.com</i></li></ul> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=638222020-10-15T21:48:59Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 83</i> to <i>Sprint 84</i></li></ul> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=643702020-10-29T19:34:07Zpulpbot
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p>PR: <a href="https://github.com/pulp/pulp_container/pull/171" class="external">https://github.com/pulp/pulp_container/pull/171</a></p> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=644472020-10-30T15:56:57Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 84</i> to <i>Sprint 85</i></li></ul> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=645412020-11-03T12:28:55Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul><p>Applied in changeset <a class="changeset" title="Fixed Renderer to handle properly Manifest and Blob responses. closes #7620 https://pulp.plan.io..." href="https://pulp.plan.io/projects/pulp_container/repository/68/revisions/970e2cfd37ea6d5d7e21ce128750424dfe1f5af1">970e2cfd37ea6d5d7e21ce128750424dfe1f5af1</a>.</p> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=655662020-12-09T15:40:08Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>2.2.0</i></li></ul> Container Support - Issue #7620: pulpcore registry api doesn't like Accept headers when syncing from pulphttps://pulp.plan.io/issues/7620?journal_id=656632020-12-10T16:43:31Zpulpbot
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>