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.

Bug 1975858

Summary: [pulp3] Content migration is stuck at starting stage for the last 19 hours.
Product: Red Hat Satellite Reporter: Devendra Singh <desingh>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lai <ltran>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: ggainey, rchan, ttereshc
Target Milestone: UnspecifiedKeywords: Triaged
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-06-29 11:52:12 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-24 15:14:18 UTC 
Description of problem: Content migration is stuck at starting stage for the last 19 hours.


Version-Release number of selected component (if applicable):
6.9

How reproducible:
1/1

Steps to Reproduce:
1. Prepared the 6.9 setups using the customer's provided backup data.
2. Ran the pulp migration.
3. Pulp migration failed due to the "cursor not found" issue, applied the workaround mentioned at BZ#1972998.
4. Re-ran the pulp migration again but it is in the "Content migration starting" stage for the last 19 hours. 

Actual results:
Content migration is stuck at "Content migration starting" for more than 19 hours.  

Expected results:
Content migration should not be stuck at "Content migration starting"

Additional info:
Comment 2 Tanya Tereshchenko 2021-06-29 11:52:12 UTC 
Task was assigned to a removed worker.
The issue is tracked as a part of BZ#1962462.

*** This bug has been marked as a duplicate of bug 1962462 ***
Comment 3 pulp-infra@redhat.com 2021-10-12 14:08:48 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2021-10-12 14:08:49 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.