Bug 1199967

Summary:	[RFE] Pulp takks between Satellite and Capsules must provide keepalive mechanism
Product:	Red Hat Satellite	Reporter:	Benjamin Chardi <bchardim>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	dzhukous, mmccune
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-10 16:40:30 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 Benjamin Chardi 2015-03-09 12:03:13 UTC

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.

Comment 1 RHEL Program Management 2015-03-09 12:13:14 UTC

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.

Comment 4 Mike McCune 2015-03-10 16:40:30 UTC

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

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