Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: pulp3 migration failed with "Katello::Errors::Pulp3Error: Cursor not found" error.
Version-Release number of selected component (if applicable):
6.9.z
How reproducible:
always with a specific database
Steps to Reproduce:
1. Prepare the 6.9.z setup using the upgrade template.
2. Run the pre-migration steps before running the upgrade for 6.10 snap5.
3. Applied the patch for BZ#1967131
4. run the pulp migration and it failed with "Katello::Errors::Pulp3Error: Cursor not found" error.
Actual results:
pulp3 migration failed with " Katello::Errors::Pulp3Error: Cursor not found" error.
Expected results:
pulp3 migration should be completed successfully.
Additional info:
Comment 2Tanya Tereshchenko
2021-06-17 14:09:09 UTC
What is the value of the CONTENT_PREMIGRATION_BATCH_SIZE in the /etc/pulp/settings.py
This happens sometimes on the slow I/O system (with HDD) and the batch for premigration should be decreased in such case.
If it's quite low already (e.g. 50), just re-run content prepare.
Comment 7Tanya Tereshchenko
2021-06-21 16:54:29 UTC
To be clear, there is nothing to be done here code wise.
If a system runs into the problem, a pulp setting should be adjusted according to https://gist.github.com/jlsherrill/19003b646c9d4a1623da301e46ec2263 .
This is done, so the systems where I/O is fast enough, were able to benefit from faster migration.
A low default to the CONTENT_PREMIGRATION_BATCH_SIZE will make all systems to migrate sloooower.
This needs a KCS or docs change, what is the usual way of handling such things, tuning guide?