Issue #8133
closed
Same package from different repos yields error on sync
Status:
CLOSED - CURRENTRELEASE
- Related to Issue #7208: Error during sync : Path is duplicated added
- Triaged changed from No to Yes
- Related to Issue #7507: Pulp RPM 3.6.2 - ValueError: Cannot create repository version. Path is duplicated added
After a thorough cleaning - removing the offending package, deleting all repoversions where it was present and deleting orphans - I can no longer reproduce this error. I suspect there was something in the metadata from my pulp2 migration that caused this.
I have the same issue with syncing postgresql and grafana. What can we do to bring this forward?
trendyandy wrote:
I have the same issue with syncing postgresql and grafana. What can we do to bring this forward?
we are impacted by this, also with Grafana repo
Especially for Katello users in this thread, it would be good to know if Pulpcore 3.14 helps out with this issue. Katello 4.1 is now on Pulpcore 3.14 (and related plugins).
Briefly checked: on 4.1.1 with pulpcore 3.14. grafana sync this morning:
No declared artifact with relative path "grafana-2.6.0.x86_64.rpm" for content "<Package: grafana>"
- Project changed from RPM Support to Pulp
The fix for this particular failure-scenario is in artifact_stages in pulpcore. Switching to the correct project.
- Status changed from NEW to POST
- Assignee set to ggainey
- Sprint/Milestone set to 3.15.0
- Sprint set to Sprint 101
- Copied to Issue #9130: Backport #8133 "Same package from different repos yields error on sync" to 3.14.z added
- Sprint changed from Sprint 101 to Sprint 102
- Status changed from POST to MODIFIED
- Copied to Backport #9227: Backport #8133 "Same package from different repos yields error on sync" to 3.7.z added
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Related to Backport #9446: Backport #8133 "Same package from different repos yields error on sync" to 3.9.z added
Also available in: Atom
PDF
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.
fixes #8133