The deb migration pipeline cannot successfully skip corrupted content
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).
#1 Updated by quba42 about 2 months ago
- Status changed from NEW to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|1ad1be59ddfa43d11eb7e9a26c62004ade5f3d6d.
Please register to edit this issue