Project

Profile

Help

Story #5731

closed

Syncing creates RepositoryContent records even if no content was actually added

Added by daviddavis about 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Problem

The workflow we have for errata merge:

1. During sync, we create new errata records and associate them to a repo version via RepositoryContent
2. In finalize_new_version we merge errata in the new version
3. Then we remove original errata which may have been just added in step 1

The problem is that the RepositoryContent content in step 1 still gets created and therefore will exist. It's useless and misleading to users. We have to add an extra step in pulp_rpm to delete these records.

Solution

In pulpcore, after finalize_new_version gets called, add a step which deletes any of these RepositoryContent where version_added and version_removed both point to your new version.


Related issues

Is duplicate of Pulp - Issue #5707: base_version can cause content can show as being added and removed in the same versionCLOSED - CURRENTRELEASEgmbnomisActions

Also available in: Atom PDF