Issue #5924
closed
Advisory conflict resolution affects mirror sync case
Description
Currently advisory conflict resolution assumes that advisories from a base/previous version are always present in the new one. It might not always be the case (e.g. mirror case). Current behaviour leads to wrong results - either more advisories are present than needed, or the error is raised due to inability to resolve advisory conflicts.
resolve_advisories should check whether any conflicts are present in the current version and only then, look into previous version for such advisories to figure out which ones were present before and which ones are being added.
Updated by ttereshc over 4 years ago
Related to conversation on the mailing list https://www.redhat.com/archives/pulp-dev/2019-December/msg00058.html
Updated by ppicka about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ppicka
- Sprint set to Sprint 64
Updated by ppicka about 4 years ago
- Status changed from ASSIGNED to POST
Added by ppicka about 4 years ago
Updated by ppicka about 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset 33761b7966187ebab056c9f028f50f69fe591ba6.
Updated by ttereshc about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Advisory conflict resolution
Advisory conflict resolution now check current version first if advisory resolution is needed.
Required PR: https://github.com/pulp/pulp_rpm/pull/1568
closes: #5924 https://pulp.plan.io/issues/5924