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.
Bug 1268318 - qdrouter on clients needs to handle torn down connections on port 5646
Summary: qdrouter on clients needs to handle torn down connections on port 5646
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-02 13:51 UTC by Stuart Auchterlonie
Modified: 2019-09-12 09:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-05 15:33:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stuart Auchterlonie 2015-10-02 13:51:09 UTC
Description of problem:

Following on from
https://bugzilla.redhat.com/show_bug.cgi?id=1249890

I was mentioned that this issue would affect clients to,
see comments #13, #18, #20, #31, #32

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

6.1.2 plus hotfix from https://bugzilla.redhat.com/show_bug.cgi?id=1249890

How reproducible:

100%

Steps to Reproduce:
1. Have client connected to satellite. Uses port :5646
2. Simulate dropped connection. I used iptables to drop all :5646 
   traffic from the client system
3. Satellite / Capsule side will drop and clean up the connections
   with the hotfix in place, the client side does not.

Actual results:

Client systems still think their connection is open, when it has
been torn down.

Expected results:

Client systems deal with torn down connections to the sat / capsule
and reconnect


Additional info:

Client system: 192.168.160.186 (appear to Satellite at 10.33.1.59 due to NAT)
Satellite sys: 10.33.9.118

Initial State:
- Client:
# netstat -tanp | grep :5646
tcp        0   5956 192.168.160.186:52656   10.33.9.118:5646        ESTABLISHED 14862/qdrouterd     
- Satellite:
# netstat -tanp | grep :5646
...   
tcp        0      0 10.33.9.118:5646        10.33.1.59:52656        ESTABLISHED 18866/qdrouterd 

Add iptables rules:
- Satellite netstat changes to
tcp        0   4597 10.33.9.118:5646        10.33.1.59:52656        FIN_WAIT1   - 
before disappearing completely shortly aftwards.

Client system still has
tcp        0      0 192.168.160.186:53051   10.33.9.118:5646        ESTABLISHED 14862/qdrouterd

Comment 2 Stuart Auchterlonie 2015-10-05 15:33:51 UTC
Faulty testing methodology, going to re-raise with proper data


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