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 1031223

Summary:	hard coded limit of 64 masters in agreement and changelog code
Product:	Red Hat Enterprise Linux 7	Reporter:	Nathan Kinder <nkinder>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jgalipea, mreynolds, nhosoi, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.1.6-12.el7	Doc Type:	Bug Fix
Doc Text:	Cause: Need for more than 64 replication masters. Consequence: Not able to use more than 64 masters Fix: Allow unlimited number of masters. Result: Replication deployments can now use as many master as needed.	Story Points:	---
Clone Of:	1031222	Environment:
Last Closed:	2014-06-13 12:08:03 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:	1031222
Bug Blocks:

Description Nathan Kinder 2013-11-15 23:05:08 UTC

+++ This bug was initially created as a clone of Bug #1031222 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47587

repl5.h:
#define MAX_NUM_OF_MASTERS		64

repl5_agmt.c:
typedef struct repl5agmt {
...
	struct changecounter *changecounters[MAX_NUM_OF_MASTERS]; /* changes sent/skipped since server start up */
...
}

cl5_cache.c:
struct clc_buffer {
...
	struct csn_seq_ctrl_block *buf_cscbs [MAX_NUM_OF_MASTERS];
}

Comment 1 Sankar Ramalingam 2013-11-25 17:41:02 UTC

Request you to add steps to verify buzilla.

Comment 3 mreynolds 2013-12-11 17:35:09 UTC

Not sure how easy this is to reproduce, as you need to set up more than 64 master directory servers.

Steps:

[1]  Create 65 servers
[2]  Setup MMR replication between all of them
[3]  Verify replication is working between all the servers

Comment 5 Sankar Ramalingam 2014-02-07 13:34:10 UTC

Adding qe_test_coverage+ flag

Comment 6 Ludek Smid 2014-06-13 12:08:03 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.