Backport to 3.7 artifact stage fixes which affect pulp 2to3 migration
Adds additional d_artifact.remote check
Not all d_artifact objects have remotes, e.g. the migration plugin does
not. Other places in the code account for this, but there is one area
that does not. This adds an additional check to one codepath that checks
for equality of
d_artifact.remote.pk only if
(cherry picked from commit 25745275c0f3a7bd832946749ed27381694d612f)
Fixed artifact_stages edge case for multi-artifact/multi-remote batches.
Only encountered when 2to3-migrating specific content in specific orders.
(cherry picked from commit b23c9294b9ed555078053b4968ed5b933ab1e9c9)
Please register to edit this issue