Actions
Backport #9227
closed
Backport #8133 "Same package from different repos yields error on sync" to 3.7.z
Start date:
Due date:
% Done:
100%
Estimated time:
Triaged:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 103
Quarter:
Related issues
Updated by ttereshc over 3 years ago
- Copied from Issue #8133: Same package from different repos yields error on sync added
Updated by ttereshc over 3 years ago
- Related to Backport #9228: Backport the relative path fix "fix_mismatched_remote_artifacts" to 3.11.z added
Updated by pulpbot about 3 years ago
- Status changed from NEW to POST
Added by ttereshc about 3 years ago
Updated by ttereshc about 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|16d9cd110b63b486ac0b606482e42718cdf79d4c.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by jsherril@redhat.com about 3 years ago
- Copied to Backport #9446: Backport #8133 "Same package from different repos yields error on sync" to 3.9.z added
Actions
.
Loosens the constraints around what can be in a new-repository-version.
There are RPM repositories "in the wild" that violate Pulp's assumptions about what is 'legal' in an incoming repository version. This commit changes some fatal errors into log-warnings, along with some heuristics around how to get a 'reasonable' repository in the face of suboptimal data.
To control activation of this behavior, RemoteArtifactSaver recognizes a ctor-keyword "fix_mismatched_remote_artifacts". This defaults to False; if provided as True, invokes the new behavior.
This change also adds handling for an exception during repo-version-failure-cleanup that could result in losing error info.
backports #8133
fixes #9227
(cherry picked from commit 349f2137d970f87190749b417cfa137dc0f99ff5)