Actions
Issue #3233
closed
Story #3209: As a user, I have Repository Versions
Version incorrectly says that it removed a content unit
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 31
Quarter:
Description
The squash code has a bug. Suppose you have 3 repo versions. Version 1 adds a unit, version 2 removes the unit, and version 3 re-adds the unit. If you remove version 2 then you have 2 RepositoryContent records pointing to version 3—one where version_removed is version 3 (but version_added is still version 1) and one where version_added is version 3. So the unit appears in 'removed' but is still in version 3's content.
Actions
.
Update repo version squash logic to deal with content removed but readded
Repo version squash should be resolved according to this design: https://github.com/pulp/pulp/pull/3228#issuecomment-347659974
fixes #3233 https://pulp.plan.io/issues/3233