Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
As like Lazy sync provides different download policies for rpm repositories, Need download policies for docker images.
Same way it should happen with the capsule.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
When adding docker repositories, need to sync entire repo including all images which are not needed.
Currently, most of the information downloaded from the docker repositories is not needed or outdated (old OCP image versions). Also, It takes a lot of time for the capsules to Sync this huge volume of information.
Expected results:
Like to choose what to download from registry/docker repo.
Able to set download policies (Lazy sync for rpm) like On-demand, immediate, background.
Additional info:
Comment 2pulp-infra@redhat.com
2017-10-24 12:32:03 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2017-10-24 12:32:06 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
This feature will be available when pulp-3 is available in Sat-6 but there is no release timeline for that.
I am hopeful a complimentary feature will be available in an upcoming release of Sat-6 where a set of tags may be whitelisted to sync.
Comment 19pulp-infra@redhat.com
2021-03-05 23:09:54 UTC
The Pulp upstream bug status is at CLOSED - WONTFIX. Updating the external tracker on this bug.