Description of problem:
To ensure data correctness, pulp 2to3 migration requires fetching content in ordered way
no index for _last_updated on content models causes a fatal error when ordered result is queried.
Version-Release number of selected component (if applicable):
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.
Steps to verify:
1. Sync couple of large repositories with Pulp <= 2.21.4, e.g. RHEL7 and RHEL8 BaseOS and Appstream
2. Try to run migration from pulp 2 to pulp 3 using pulp-2to3-migration>=0.7.0.
It should fail.
Upgrade pulp2 to 2.21.5 and run migration again, observe no failure.
Not sure if the combinations of versions required to test it exist with the product.
In the worst case, you can just check that the same steps just for pulp 2.21.5 and pulp-2to3-migration >= 0.7.0 produce no error.
Steps to retest:
As mentioned in comment #9 above, I have followed her steps, but only did RHEL8 BaseOS and Appstream. The syncing and migration was both successfull on pulp-rpm-plugins-2.21.5-2.el7sat.noarch, pulp-server-2.21.5-2.el7sat.noarch, and python3-pulp-2to3-migration-0.9.1-1.el7pc.noarch.
Verified on 6.9.0_017
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.