Actions
Issue #9130
closed
Backport #8133 "Same package from different repos yields error on sync" to 3.14.z
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 102
Quarter:
Related issues
Updated by dalley over 3 years ago
- Copied from Issue #8133: Same package from different repos yields error on sync added
Updated by dalley over 3 years ago
- Assignee deleted (
ggainey) - Sprint/Milestone changed from 3.15.0 to 3.14.3
Updated by ipanova@redhat.com over 3 years ago
- Sprint changed from Sprint 101 to Sprint 102
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Added by dalley over 3 years ago
Updated by dalley over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|d44ea6d767c07196fdbe5a7dc1749d9a30852c99.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
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 #9130
(cherry picked from commit 349f2137d970f87190749b417cfa137dc0f99ff5)