Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #1449

closed

Users cannot sync v1 content from a registry that implements the v2 API

Added by rbarlow over 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
rbarlow
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Docker:
Platform Release:
2.8.0
Target Release - Docker:
2.0.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

The current Pulp sync implementation tries to use the remote registry via the v2 API, and if the registry does not implement v2 it falls back to v1. However, if the registry does implement v2, v1 is never tried. Satellite 6 plans to use pulp_docker's sync function instead of Nodes to move content from a parent to a capsule. Due to the current implementation, any repositories that have v1 and v2 content will only be able to mirror v2 content into the capsule.

When fixing this issue, consider whether it would be advantageous or not to make the fallback behavior a boolean option. Not making it optional has the advantage of being simpler (no additional settings needed). Making it optional has the advantage of giving users control in situations where perhaps they only want to use the v2 API and don't want all the images downloaded twice. You are somebody's kid, do what you think is right.

Actions
Send by e-mail Copy link

Also available in: Atom PDF