Bug 1303037 - portblock resource-agent
Summary: portblock resource-agent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.3
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1302545 1337109
Blocks: 1278336 1330218 1354439 1363722
TreeView+ depends on / blocked
 
Reported: 2016-01-29 11:44 UTC by Oyvind Albrigtsen
Modified: 2016-11-04 00:01 UTC (History)
11 users (show)

Fixed In Version: resource-agents-3.9.5-82.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1302545
Environment:
Last Closed: 2016-11-04 00:01:10 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2174 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2016-11-03 13:16:36 UTC

Comment 2 Oyvind Albrigtsen 2016-01-29 12:34:04 UTC
Tested resource agent from upstream and verified that it's working on RHEL7.

Comment 4 Oyvind Albrigtsen 2016-02-22 12:08:40 UTC
The easiest example would be to simply block one of the ports for a service:
# pcs resource create VIP IPaddr2 ip=192.168.122.122
# pcs resource create pb ocf:heartbeat:portblock protocol=tcp portno=3306 action=block ip=192.168.122.122
# pcs resource create NFS nfsserver
# pcs resource group add NFS-group VIP pb NFS
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
DROP       tcp  --  anywhere             HOSTNAME              multiport dports mysql

I'm using a MySQL port in this example to avoid NFS failing.

Comment 9 Oyvind Albrigtsen 2016-09-16 09:17:16 UTC
Tested and working patch: https://github.com/ClusterLabs/resource-agents/pull/845

Comment 13 errata-xmlrpc 2016-11-04 00:01:10 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-2174.html


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