Actions
Issue #8778
closedSet pulp repo distributor last_publish to publish start time instead of finish time
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
This is related ticket https://pulp.plan.io/issues/5951 for previous fix of the problem. The current fix relates to https://projects.engineering.redhat.com/browse/RHELDST-5086.
The problematic content type here is erratum that is shared with more than one repository. When this erratum gets updated, pulp will set last_unit_added to all affected repos, including those currently in publish (afaict only erratum type units behave like this). So the subsequent fast-forward publish will be skipped because the erratum was updated during publish.
This problem can be fixed by setting repo distributor last_publish to publish start time instead of finish time.
Updated by ipanova@redhat.com over 2 years ago
- Status changed from NEW to POST
- Assignee set to rbikar
- Tags Pulp 2 added
Added by rbikar over 2 years ago
Updated by rbikar over 2 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp|dde56335ea622adecab081e4032f75549cb0dc6f.
Actions
Set last_publish as a start of publish [RHELDST-5086, #8778]
When a repository is published, set last_publish field on distributor to the start time of publish instead of finish time. This fix relates to erraum content type which can be updated even if a repo is in publish.
With this change pulp shouldn't falsely skip publish of a repo when last_unit_added is set to time between publish start and finish.
Closes #8778 https://pulp.plan.io/issues/8778