Bug 1972998

Summary:	pulp3 migration failed with "Katello::Errors::Pulp3Error: Cursor not found"
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Lai <ltran>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	ahumbe, ttereshc
Target Milestone:	Unspecified	Keywords:	PrioBumpGSS, UpgradeBlocker
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-01 15:09:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Devendra Singh 2021-06-17 04:16:18 UTC

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 2 Tanya 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 7 Tanya 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?

Comment 11 Brad Buckingham 2021-07-01 15:09:11 UTC


*** This bug has been marked as a duplicate of bug 1944317 ***