Actions
Issue #2616
closed
after sync with remove_missing option the next publish is no-op sometimes
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Steps to reproduce:
- create repo A with feed, sync, publish
- create repo B with feed pointed to repo A and remove_missing enabled, sync
- remove any units from repo A, publish
- re-sync repo B
- observe negative removed_count in sync report
{
...
"added_count": 0,
"updated_count": 0,
"removed_count": -2
}
- for puppet plugin it will result in no-op publish
The calculation of `removed_count` is done here
which explains how it can be negative.
Check for update `last_units_removed` relies on removed_count being positive.
If the only change during the sync was a removal of some units, the next publish will be no-op, because `last_units_removed` timestamp was not updated.
Actions
.