Bug 1249890 - Support heartbeats on qpid 5647 port
Summary: Support heartbeats on qpid 5647 port
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.0.8
Hardware: All
OS: Linux
high vote
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Depends On:
TreeView+ depends on / blocked
Reported: 2015-08-04 03:54 UTC by Amit Upadhye
Modified: 2021-04-06 18:01 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-10-15 18:20:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
hotfix packages (1.59 MB, application/x-gzip)
2015-10-01 15:04 UTC, Mike McCune
no flags Details
hotfix packages RHEL6 (1.61 MB, application/x-gzip)
2015-10-08 15:15 UTC, Mike McCune
no flags Details

System ID Private Priority Status Summary Last Updated
Pulp Redmine 1232 0 High CLOSED - CURRENTRELEASE Enable heartbeats in the proton messaging adapter in goferd Never
Red Hat Knowledge Base (Solution) 1554243 0 None None None Never
Red Hat Product Errata RHBA-2015:1911 0 normal SHIPPED_LIVE Satellite 6.1.3 bug fix update 2015-10-15 22:19:19 UTC

Description Amit Upadhye 2015-08-04 03:54:48 UTC
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?  

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

9. Is the sales team involved in this request and do they have any additional input?  


10. List any affected packages or components.  


11. Would the customer be able to assist in testing this functionality if implemented?


Comment 19 Stephen Benjamin 2015-08-05 00:10:11 UTC
Created redmine issue http://projects.theforeman.org/issues/11291 from this bug

Comment 29 pulp-infra@redhat.com 2015-09-03 19:00:19 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 30 pulp-infra@redhat.com 2015-09-03 19:00:21 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

Comment 33 pulp-infra@redhat.com 2015-09-10 17:30:23 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.

Comment 36 pulp-infra@redhat.com 2015-09-11 19:30:16 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 38 pulp-infra@redhat.com 2015-09-24 16:00:24 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 40 Mike McCune 2015-10-01 14:59:22 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:


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 41 Stuart 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?"

Comment 42 Mike McCune 2015-10-01 15:04:42 UTC
Created attachment 1079186 [details]
hotfix packages

Comment 50 Corey Welton 2015-10-05 15:18:56 UTC
QE notes:  test with a configuration where there is a firewall between capsule and server, where idle connections are dropped.

Comment 52 Tazim Kolhar 2015-10-06 11:29:03 UTC

    please provide verification steps

thanks and regards,

Comment 53 jcallaha 2015-10-07 18:48:23 UTC
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.

Comment 54 Mike McCune 2015-10-08 15:15:51 UTC
Created attachment 1081045 [details]
hotfix packages RHEL6

Comment 56 errata-xmlrpc 2015-10-15 18:20:33 UTC
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.


Comment 57 pulp-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.

Note You need to log in before you can comment on or make changes to this bug.