RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1195500 - pacemaker implement libqb server side buffer enhancements
Summary: pacemaker implement libqb server side buffer enhancements
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pacemaker
Version: 6.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 6.8
Assignee: Andrew Beekhof
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1110042 1110043
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-23 23:05 UTC by David Vossel
Modified: 2016-05-10 23:51 UTC (History)
11 users (show)

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:
Clone Of: 1110042
Environment:
Last Closed: 2016-05-10 23:51:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0856 0 normal SHIPPED_LIVE pacemaker bug fix and enhancement update 2016-05-10 22:44:25 UTC

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
Note You need to log in before you can comment on or make changes to this bug.