Description of problem: Currently, if you generate a PULP_MANIFEST and sync from another location via URL, you will receive the files in the Manifest and they will become locally available on the Satellite, but if you UPDATE a file that has already been imported and regenerate the PULP_MANIFEST, then sync again, the Satellite's versions of the manifest will have a duplicate file name entry with separate sha256sums and sizes, but will not retrieve the new file (It will maintain the original in the repo). Version-Release number of selected component (if applicable): nightly How reproducible: 100% Steps to Reproduce: 1. Generate PULP_MANIFEST and sync a File repo from a http based URL 2. Make a change to a file (text file, etc..), but DO NOT change the file NAME. 3. Re-Generate the PULP_MANIFEST for the remote file repo, and then re-sync on Satellite. Actual results: File that was modified will have two entries on the PULP_MANIFEST inside the local Satellite copy of the repo with separate sha256sums and sizes, but identical name, and only the original copy of the file prior to editing will exist in the repo. Expected results: We should replace original file with the newest checksum. (Act like mirror-on-sync?) Additional info: Perhaps the File repo type should be able to determine the time of PULP_MANIFEST generation and make a determination about what should exist based off of that? (i.e. Include a date inside the PULP_MANIFEST on creation)
Can you add the specific Pulp version that was in use? Thanks!
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Michael, During this test I had: pulp-server-2.9.3-2.el7sat.noarch
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. 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.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
FailedQA with Sat6.3, snap 17. Thanks for advice to rplevka. As manipulating Pulp directly is not supported is Satellite, we can use the following reproducer: 1) Create Product 2) In Product, create Repo1 with empty URL 3) Upload File to Repo1 4) In Product, create Repo2 with URL=<content_url_of_repo_1> [1] 5) Sync Repo2 6) Change contents of File 7) In any of Repo1 or Repo2 (works both ways), upload File 8) Sync Repo2 again 9) In content URL of Repo2, view contents of PULP_MANIFEST file Actual results: Two entries with the same filename and different hash Expected results: Not sure... how do we decide which version of the file to keep? [1] for example, http://<FQDN>/pulp/isos/e2f04116-1ce6-4390-a781-75d00299c57f/
Requesting needsinfo from upstream developer daviddavis because the 'FailedQA' flag is set.
Found the bug and opened a new upstream issue.
Upstream bug is fixed and merged, moving to POST
Verified with Sat6.3 snap 20. Used reproducer from comment 12. After that, there were only the ew file's metadata and only the new file in both repositories.
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/RHSA-2018:0336