Description of problem: If I cancel a task at pre-migration stage or if there is a failure at pre-migration time, the next migration re-run won't continue properly. It will skip content based on its last_updated timestamp. We need to pre-migrate content ordered by last_updated date to avoid this. Version-Release number of selected component (if applicable): pulp-2to3-migration 0.6.0
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
There's no real reliable way of reproducing the issue. I have checked that the code is present in the build. Verified on 6.9.0_017 with python3-pulp-2to3-migration-0.9.1-1.el7pc.noarch.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:1313