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:
Observing capsule sync issues.  Customer has two capsules, one capsule is not working at all.  The tasks are build and sent to the capsule, celery assigns them to pulp workers, but nothing else happens from here.  The task eventually returns a timeout.  This is true for both content publish/promote automated syncs and manual syncs.  

The second capsule appears to work fine for publish/promote automated tasks, but--as observed this morning--manual syncs seem to get stuck.

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

How reproducible:
Every time

Steps to Reproduce:
1. Initiate a publish/promote/manual sync
2. Watch celery and pulp-admin
3. Monitor task for timeout

Actual results:
Thanks hang, eventually become paused or fail.

Expected results:

Additional info:
Issue has been open since 6/28. Customer pushing for resolution.

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

The Capsule Synchronization has thrown an error or has been running for a very long time without any progress.

If there is no error related to the Synchronization Task(s) and you simply want to validate the content that was synced, regards https://gbwhatsapp.fun/