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.
When syncing a repo with download policy of on_demand, if it associates units to the repo that were already in pulp's DB, the sync does not create catalog entries. It should create catalog entries at least for any units where downloaded=False.
To reproduce:
create a repo with on_demand and sync it
see catalog entries for those units in the DB
delete the repo
see there are no catalog entries for those units in the DB
re-create the same repo with on_demand and sync it
see that there are no catalog entries for those units in the DB
Comment 2pulp-infra@redhat.com
2016-05-12 13:30:43 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2016-05-12 13:30:45 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2016-05-13 15:00:37 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2016-05-19 14:00:21 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 8pulp-infra@redhat.com
2016-06-02 19:30:27 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 9pulp-infra@redhat.com
2016-06-08 20:30:26 UTC
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
Comment 11pulp-infra@redhat.com
2016-06-27 17:00:47 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
1) Created a repo with on_demand download_policy
2) saw catalog entries for those units in the DB
Below are the commands to view the catalog entries.
a) mongo pulp_database
b) db.lazy_content_catalog.find()
3) deleted the repo
4) saw there are no catalog entries for those units in the DB
5) re-created the same repo with on_demand and synced it
6) we can again view the catalog entries for those units in the DB
VERIFIED With sat623-snap2
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, 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/RHBA-2016:2108
When syncing a repo with download policy of on_demand, if it associates units to the repo that were already in pulp's DB, the sync does not create catalog entries. It should create catalog entries at least for any units where downloaded=False. To reproduce: create a repo with on_demand and sync it see catalog entries for those units in the DB delete the repo see there are no catalog entries for those units in the DB re-create the same repo with on_demand and sync it see that there are no catalog entries for those units in the DB