Bug 1195500

Summary:	pacemaker implement libqb server side buffer enhancements
Product:	Red Hat Enterprise Linux 6	Reporter:	David Vossel <dvossel>
Component:	pacemaker	Assignee:	Andrew Beekhof <abeekhof>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.7	CC:	abeekhof, cfeist, cluster-maint, djansa, fdinitto, jkortus, kgaillot, kwenning, mspqa-list, salmy, tlavigne
Target Milestone:	rc
Target Release:	6.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pacemaker-1.1.14-4.el6	Doc Type:	Enhancement
Doc Text:	Feature: Pacemaker now supports IPC message sizes larger than 1MB, allowing it to handle more complex cluster configurations with large numbers of nodes and resources. Reason: Result:	Story Points:	---
Clone Of:	1110042	Environment:
Last Closed:	2016-05-10 23:51:18 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:	1110042, 1110043
Bug Blocks:

Comment 4 Andrew Beekhof 2015-03-02 23:30:30 UTC

No capacity. Bumping to 6.8

Comment 5 Andrew Beekhof 2015-03-31 01:31:15 UTC

Do we need anything other than a rebuild for this?

Comment 10 Ken Gaillot 2016-01-12 18:32:29 UTC

This is basically a 6.7 clone of BZ 1174462 , which was fixed upstream in d9a51c6 and is included in the latest 6.8 build.

Comment 15 Klaus Wenninger 2016-03-16 19:54:52 UTC

I had put the pacemaker-build 1.1.14-3.0 temporarily in the buildroot.
That shouldn't have any influence on the build of pacemaker itself.

Anyway reading the first entry in this thread I thought we might be
building against the wrong version of libqb out of the same reason why
I had manually put the pacemaker build into the buildroot - as there
seems to be something broken with the rhel-6.8-build leading to the 
fact that we are still building against the rpms that where initially
put in, instead of building against the current packages.
So I tried to build locally against the nightly from March 9th but the
output was the same.

Comment 17 Ken Gaillot 2016-03-16 23:48:32 UTC

Upstream commit 0fe7a4dd inadvertently disabled the fix for this issue. Upstream commit eff1024 reverts that commit, and will be backported to fix this issue.

Comment 18 Ken Gaillot 2016-03-17 15:46:11 UTC

Updated build available

Comment 22 errata-xmlrpc 2016-05-10 23:51:18 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-0856.html