Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1174462

Summary: RFE: remove 1M message size limit
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Kortus <jkortus>
Component: pacemakerAssignee: David Vossel <dvossel>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 7.1CC: abeekhof, cluster-maint, djansa, dmach, dvossel, fdinitto, florian, jfriesse, mnovacek, mspqa-list, ovasik
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.1   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: pacemaker-1.1.12-15.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 975903 Environment:
Last Closed: 2015-03-05 10:00:31 UTC Type: ---
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: 975903    
Bug Blocks:    

Comment 1 David Vossel 2014-12-15 21:34:34 UTC 
upstream patch.

https://github.com/davidvossel/pacemaker/commit/d9a51c61854a1a2ec800b484e1e717239832491f
Comment 6 michal novacek 2015-01-07 14:12:26 UTC 
I have verified that there is no more 1M message size limit with pacemaker-1.1.12-15.el7.x86_64

-----

[root@marathon-01 ~]# rpm -q pacemaker
pacemaker-1.1.12-15.el7.x86_64

[root@marathon-01 ~]# pcs status
Cluster name: STSRHTS2253
Last updated: Wed Jan  7 08:11:09 2015
Last change: Wed Jan  7 08:09:24 2015
Stack: corosync
Current DC: marathon-01 (1) - partition with quorum
Version: 1.1.12-a14efad
2 Nodes configured
7 Resources configured

Online: [ marathon-01 marathon-02 ]

Full list of resources:

fence-marathon-01      (stonith:fence_apc):    Started marathon-01 
fence-marathon-02      (stonith:fence_apc):    Started marathon-02 
Clone Set: dlm-clone [dlm]
 Started: [ marathon-01 marathon-02 ]
Clone Set: clvmd-clone [clvmd]
 Started: [ marathon-01 marathon-02 ]
dummy  (ocf::heartbeat:Dummy): Started marathon-01 

Failed actions:

PCSD Status:
marathon-01: Online
marathon-02: Online

Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled

[root@marathon-01 ~]# for x in `seq 1 20`; do pcs resource meta dummy x$x="`openssl rand -hex 32000`" || break; echo $x done; done
1 done
2 done
3 done
4 done
5 done
6 done
7 done
8 done
9 done
10 done
11 done
12 done
13 done
14 done
15 done
16 done
17 done
18 done
19 done
20 done
Comment 11 errata-xmlrpc 2015-03-05 10:00:31 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-2015-0440.html