0.2.0 70% 20 issues (14 closed — 6 open) Related issues Issue #5374: re-run of migration tooling has incorrect counts Actions Issue #6111: Re-migrations take nearly as long as initial migrations Actions Issue #6469: exceptions encountered during migration run are not captured in a task Actions Issue #6511: Content which depends on the pulp2 repo content is not skipped when its repo is not migrated Actions Issue #6935: Validation failure reports incorrect resources if there are multiple distributors specified Actions Issue #6949: Re-migration of a distribution tree fails Actions Issue #6950: Migration of a distribution tree fails when it is present in multiple repos Actions Issue #6951: Migration of a distribution tree fails if it has a treeinfo and not .treenfo Actions Issue #7053: Error migrating after cloning repo contents: Pulp2Repository matching query does not exist. Actions Issue #7092: re-migration of errata that have now been copied to new repositories are not migrated for those new repositories Actions Issue #7093: yum metadata file not being migrated Actions Issue #7260: Re-migration of a distribution tree fails when not all LCE have been migrated Actions Task #6516: Automatically produce a "complex" migration plan from "simple" migration plans Actions Task #6939: Ensure that all the `size` fields are BigIntergerField to match the pulpcore `Artifact.size` Actions Task #6963: Add a function for cleaning up database between migration plugin tests Actions Task #7009: Do not create a child task for already migrated repos Actions Task #7020: Adjust comps.xml migration pipeline and do not create relations Actions Story #6769: As a user, I can track the progress of pulp2->pulp3 migrations Actions Story #6813: As a user, the checksum type configuration for RPM distributors is migrated Actions Story #6927: As a user, I can migrate Remotes for SLES repos Actions
.
.
.