Issue #8612
closedThe deb migration pipeline cannot successfully skip corrupted content
Description
Running a 2ot3 migration for deb content with skip_corrupted=True
will result in the following error (if there actually is corrupted content):
pulp_deb.app.models.content.PackageReleaseComponent.package.RelatedObjectDoesNotExist: PackageReleaseComponent has no package.
This is because the PackageReleaseComponent still tries to record a relation to the skipped package.
This is a possible duplicate of: https://pulp.plan.io/issues/8562 (the different manifestations could be a result of different pulpcore versions, or it is a completely unrelated issue).
Added by quba42 over 3 years ago
Added by quba42 over 3 years ago
Revision 1ad1be59 | View on GitHub
Skip PackageReleaseComponents if Package was skipped
Added by quba42 over 3 years ago
Revision 1ad1be59 | View on GitHub
Skip PackageReleaseComponents if Package was skipped
Updated by quba42 over 3 years ago
- Status changed from NEW to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|1ad1be59ddfa43d11eb7e9a26c62004ade5f3d6d.
Added by quba42 over 3 years ago
Revision 1988dd6e | View on GitHub
Skip PackageReleaseComponents if Package was skipped
fixes #8612 https://pulp.plan.io/issues/8612
(cherry picked from commit 1ad1be59ddfa43d11eb7e9a26c62004ade5f3d6d)
Added by quba42 over 3 years ago
Revision 1988dd6e | View on GitHub
Skip PackageReleaseComponents if Package was skipped
fixes #8612 https://pulp.plan.io/issues/8612
(cherry picked from commit 1ad1be59ddfa43d11eb7e9a26c62004ade5f3d6d)
Added by quba42 over 3 years ago
Revision 1988dd6e | View on GitHub
Skip PackageReleaseComponents if Package was skipped
fixes #8612 https://pulp.plan.io/issues/8612
(cherry picked from commit 1ad1be59ddfa43d11eb7e9a26c62004ade5f3d6d)
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Skip PackageReleaseComponents if Package was skipped
fixes #8612 https://pulp.plan.io/issues/8612