Bug 1329547 - portblock resource-agent does not send tickling tcp packets to a client connected on port specified by portblock's option
Summary: portblock resource-agent does not send tickling tcp packets to a client conne...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents
Version: 6.8
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1327662
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-22 08:16 UTC by Marcel Kolaja
Modified: 2016-05-10 04:19 UTC (History)
10 users (show)

Fixed In Version: resource-agents-3.9.5-34.el6_8.2
Doc Type: Bug Fix
Doc Text:
Previously, the portblock resource agent did not send tickling Transmission Control Protocol (TCP) packets to clients connected to the specified port. The underlying code has been modified to ensure the tickle_tcp utility sends tickling TCP packets as required. As a result, the portblock resource agent now works as expected in the described situation.
Clone Of: 1327662
Environment:
Last Closed: 2016-05-10 04:19:51 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0993 0 normal SHIPPED_LIVE resource-agents bug fix update 2016-05-10 08:18:35 UTC

Description Marcel Kolaja 2016-04-22 08:16:04 UTC 
This bug has been copied from bug #1327662 and has been proposed
to be backported to 6.8 z-stream (EUS).
Comment 11 errata-xmlrpc 2016-05-10 04:19:51 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.

https://rhn.redhat.com/errata/RHBA-2016-0993.html
Note You need to log in before you can comment on or make changes to this bug.