Bug 1302545

Summary: Package pacemaker portblock resource-agent
Product: Red Hat Enterprise Linux 6 Reporter: Soumya Koduri <skoduri>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7CC: abeekhof, agk, cfeist, cluster-maint, fdinitto, mlisik, mnovacek, olim
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: resource-agents-3.9.5-32.el6 Doc Type: Bug Fix
Doc Text:
Cause: portblock resource agent not available in RHEL6 Consequence: Unable to simulate CTDB tickle ACKs for NFS service Fix: Add portblock resource agent Result: Able to simulate CTDB tickle ACKs
 Story Points: ---
Clone Of:
: 1303037 (view as bug list) Environment:
Last Closed: 2016-05-10 19:15:47 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:    
Bug Blocks: 1278336, 1303037, 1330218, 1354439, 1363722    

Description Soumya Koduri 2016-01-28 06:41:40 UTC 
Description of problem:
In order to simulate the behaviour of using CTDB tickle ACKs for NFS service HA correctness in pacemaker, we need portblock resource-agent script.

More details can be found in -
   https://bugzilla.redhat.com/show_bug.cgi?id=1278336#c8

Version-Release number of selected component (if applicable):
 pacemaker-1.1.12-8
Comment 2 Ken Gaillot 2016-01-28 14:55:52 UTC 
Reassigning to resource-agents component.
Comment 3 Oyvind Albrigtsen 2016-01-29 11:02:34 UTC 
Tested and verified that upstream version is working on RHEL6:
https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/portblock
Comment 4 Oyvind Albrigtsen 2016-02-25 09:58:33 UTC 
Test in: https://bugzilla.redhat.com/show_bug.cgi?id=1303037#c4
Comment 8 errata-xmlrpc 2016-05-10 19:15:47 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-0735.html