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:


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


One of our customer has a firewall between Satellite 6 and a remote Capsule. Because of corporate security rules this firewall is configured to TIMEOUT connections after 30 minutes without activity. The result is that pulp connections established between Satellite 6 central server and remote capsules timeout and CVs published from Satellite 6 central fail to publish on remote capsules.

The workaround for this problem is restart pulp-qpid-gofer services on remote capsules before starting the CVs publication.

This problem will be solved if some keepalive mechanism is implemented in pulp-qpid-gofer in order to keep alive net connections and avoid firewall timeouts.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

This is largely solved via 1169416, closing this as a dupe.

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