Description of problem Exporting a repository or library in a syncable format causes a new version to publish before completely exporting the version. This means the next time you do a "non-syncable" incremental export of the same repository, the incremental export happens from the syncable version to the latest which is incorrect. Ideally the syncable and non-syncable exports are not mixed. Version-Release number of selected component (if applicable): 6.11.z/6.12 How reproducible: Always Steps to Reproduce: 1. Create and sync a repository 2. hammer content-export complete repository --id=<repo-id> 3. Now add extra rpms to the source repo and resync 4. hammer content-export complete repository --id=<repo-id> --format=syncable 5. Finally run -> hammer content-export incremental repository --id=<repo-id> Actual results: The incremental export has no content. This is because its trying to incrementally export from Step 4 -> 5 instead of Step 1 - 3 Expected results: It incrementally exports between the repo on step 1 vs the repo in step 3 Additional info:
Connecting redmine issue https://projects.theforeman.org/issues/35369 from this bug
Upstream bug assigned to paji
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35369 has been resolved.
Library and repository incremental export continuity is not broken by exporting a syncable export. Directories with syncable exports have Label "SYNCABLE" is added into its name. VERIFIED with Satellite 6.12 SNAP10 @ RHEL8.6 The continuity is broken for Content Views - bz 2129296
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 (Important: Satellite 6.12 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-2022:8506