Bug 1303037

Summary:	portblock resource-agent
Product:	Red Hat Enterprise Linux 7	Reporter:	Oyvind Albrigtsen <oalbrigt>
Component:	resource-agents	Assignee:	Oyvind Albrigtsen <oalbrigt>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	abeekhof, agk, cluster-maint, cluster-qe, fdinitto, mlisik, mnovacek, oalbrigt, olim, skoduri, tlavigne
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	resource-agents-3.9.5-82.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1302545	Environment:
Last Closed:	2016-11-04 00:01:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1302545, 1337109
Bug Blocks:	1278336, 1330218, 1354439, 1363722

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