Hide Forgot
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
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Moving to POST as upstream fix is available.
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
The steps listed in #15 look good.
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