Project

Profile

Help

Story #5643

closed

Make schema conversion compatible with the on_demand content

Added by ipanova@redhat.com about 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Schema conversion requires config blob, in case the repo has been sycned in the on_demand option, the config_blob will not be present on the fs. We'd need to first download the config blob and then perform the conversion from schema2 to schema1

For now conversion will work with the downloaded content.

Added by Lubos Mjachky about 5 years ago

Revision 42183b9c | View on GitHub

Execute implemented schema conversion from the registry

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

Actions #1

Updated by ipanova@redhat.com about 5 years ago

  • Project changed from Docker Support to Container Support
Actions #2

Updated by lmjachky almost 5 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to lmjachky
Actions #3

Updated by ipanova@redhat.com almost 5 years ago

  • Status changed from ASSIGNED to CLOSED - CURRENTRELEASE
Actions #4

Updated by lmjachky almost 5 years ago

It was decided that pulp_container will not support the schema conversion for content synced via the on_demand policy. The registry already returns an HTTP 404 response by default if it does not succeed to fetch an associated artifact (https://github.com/pulp/pulp_container/blob/807c87d6f02ec7307c34f9f0d2ca892b9a8146b7/pulp_container/app/docker_convert.py#L265-L270, https://github.com/pulp/pulp_container/blob/807c87d6f02ec7307c34f9f0d2ca892b9a8146b7/pulp_container/app/registry.py#L241-L244).

Actions #5

Updated by ipanova@redhat.com almost 5 years ago

  • Sprint/Milestone set to 1.0.0

Also available in: Atom PDF