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.
DescriptionAnand Jambhulkar
2020-02-05 19:32:34 UTC
Created attachment 1657995[details]
With Sync Tag
Q1 - What is the exact nature of the problem trying to be solved with this request?
A1 - The initial and cron sync can be done in short time. It will be used fewer storage.
Q2 - List the business requirements.
A2 - Reduce of storage use and improve time of sync.
Q3 - Do you have specific timeline dependencies?
A3 - asap
Q4 - Can you please explain us the what are the functional requirements? If test cases can be provided this would be even more ideal.
A4 - Define a filter like 3.11.* to sync all images, that will be used in openshift 3.11.
Q5 - Would you be able to assist in testing this functionality if implemented?
A5 - Yes, we can test the implementation.
Comment 12pulp-infra@redhat.com
2020-03-23 12:08:35 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 13pulp-infra@redhat.com
2020-03-23 12:08:38 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 14pulp-infra@redhat.com
2020-03-28 12:53:37 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 15pulp-infra@redhat.com
2020-05-08 19:30:45 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 16pulp-infra@redhat.com
2020-05-08 22:14:13 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Steps to retest:
1) Create a docker repo with:
Registry URL: https://quay.io/
Upstream Repository: prometheus/busybox
2) Sync the repository
3) Look at the tags. There should be:
uclibc
latest
glibc
4) Change the repo's Limit Sync Tags to be "*c" without the quotes
5) Sync the repository again
6) Look at the tags again. Now there should be:
uclibc
glibc
7) Change the Limit Sync Tags to be "*" without the quotes
8) Sync the repo again
9) Look at the tags. There should be the same tags from step (3)
Expected:
uclibc
latest
glibc
Actual:
uclibc
latest
glibc
Verified on 6.10 snap 13
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:4702
Created attachment 1657995 [details] With Sync Tag Q1 - What is the exact nature of the problem trying to be solved with this request? A1 - The initial and cron sync can be done in short time. It will be used fewer storage. Q2 - List the business requirements. A2 - Reduce of storage use and improve time of sync. Q3 - Do you have specific timeline dependencies? A3 - asap Q4 - Can you please explain us the what are the functional requirements? If test cases can be provided this would be even more ideal. A4 - Define a filter like 3.11.* to sync all images, that will be used in openshift 3.11. Q5 - Would you be able to assist in testing this functionality if implemented? A5 - Yes, we can test the implementation.