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.
+++ This bug was initially created as a clone of Bug #1027496 +++
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47585
I have a new issue that is affecting most of my systems since the upgrade to 389-ds-base-1.2.11.15-22.el6_4.x86_64.
My systems appear to have stopped replicating new changes with one another and with replication debugging turned up, it appears that they know about the changes they have pending, but they choose not to send any of them.
There don't appear to be any errors and any other signs of issue except for the fact that changes are not propagating.
------------------------------------------------------------------------
r8202 | rmeggins | 2013-11-11 16:05:48 -0700 (Mon, 11 Nov 2013) | 2 lines
Test for upstream ticket https://fedorahosted.org/389/ticket/47585
------------------------------------------------------------------------
Comment 3Sankar Ramalingam
2014-01-30 07:34:56 UTC
(In reply to Rich Megginson from comment #1)
> ------------------------------------------------------------------------
> r8202 | rmeggins | 2013-11-11 16:05:48 -0700 (Mon, 11 Nov 2013) |
> 2 lines
>
Hi Rich, do you have automated tests in TET to verify this bug?
> Test for upstream ticket https://fedorahosted.org/389/ticket/47585
>
> ------------------------------------------------------------------------
(In reply to Sankar Ramalingam from comment #3)
> (In reply to Rich Megginson from comment #1)
> > ------------------------------------------------------------------------
> > r8202 | rmeggins | 2013-11-11 16:05:48 -0700 (Mon, 11 Nov 2013) |
> > 2 lines
> >
> Hi Rich, do you have automated tests in TET to verify this bug?
>
> > Test for upstream ticket https://fedorahosted.org/389/ticket/47585
> >
> > ------------------------------------------------------------------------
Yes, in mmrepl/cleanallruv/cleanallruv.sh ticket47585()
Thanks Rich for automating it.
mmrepl/cleanallruv/cleanallruv.sh ticket47585()
cleanallruv startup 100% (1/1)
cleanallruv run 100% (7/7)
cleanallruv cleanup 100% (1/1)
value telephoneNumber-2-0 was replicated successfully
ticket47585: cleanup
backend for o=ticket47585 is ticket47585
backend for o=ticket47585 is ticket47585
backend for o=ticket47585 is ticket47585
TestCase [ticket47585] result-> [PASS]
Hence marking as VERIFIED.
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.