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.
1. Proposed title of this feature request
Request for documentation on how to enable heartbeats on qpid 5647 port ?
2. Who is the customer behind the request?
Account: RED HAT IT/IS and acct #5243891
TAM customer: yes
SRM customer: yes
Strategic: yes
3. What is the nature and description of the request?
On Satellite 6.1 goferd connects to qdrouterd on ports 5646 and 5647. As per customer firewall torn down the 5647 connections silently after a few hours due to no traffic. Since the connection has closed without reset sent, goferd and qdrouterd on both side still thinks the connection is "active", so they didn't even try to reconnect. To avoid such issues required to add heartbeats on 5647 port too.
4. Why does the customer need this? (List the business requirements here)
To avoid silent capsule sync hangs.
5. How would the customer like to achieve this? (List the functional requirements here)
By adding heartbeats on 5647 port too.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Confirming capsule syncs are not hanging because of having heartbeats on 5647 port too.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No.
9. Is the sales team involved in this request and do they have any additional input?
No.
10. List any affected packages or components.
Unknown.
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.
Comment 19Stephen Benjamin
2015-08-05 00:10:11 UTC
== HOTFIX Instructions for RHEL7 ==
0) Download the attached tar.gz file to your Satellite and Capsules from this bugzilla, extract it to /var/tmp/qpid-heartbeat
1) On your Satellite and Capsule, configure a yum repository to point at:
[qpid-heartbeat-hotfix]
name=qpid-heartbeat-hotfix
gpgcheck=0
enabled=1
baseurl=file:///var/tmp/qpid-heartbeat
2) execute 'yum update' on both the Capsule and Satellite
3) Edit /etc/qpid-dispatch/qdrouterd.conf
Add "idle-timeout-seconds: 0" to the connector section, eg:
connector {
name: broker
addr: sat.example.com
port: 5671
sasl-mechanisms: ANONYMOUS
role: on-demand
ssl-profile: client
idle-timeout-seconds: 0
}
4) run 'katello-service restart' on the Satellite and Capsule
5) proceed with operations
Comment 41Stuart Auchterlonie
2015-10-01 15:02:11 UTC
Step 4b) run `systemctl restart goferd` on the capsules
otherwise you will pretty quickly hit the error
"Host did not respond within 20 seconds. Is katello-agent installed and goferd running on the Host?"
Verified on Satellite-6.1.0-20151006.0
In and Out connections on 5647 dropped and brought back. Was able to install and remove packages with no errors.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2015:1911
Comment 57pulp-infra@redhat.com
2015-11-09 21:00:48 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.