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 1027502 - Replication Failures related to skipped entries due to cleaned rids
Summary: Replication Failures related to skipped entries due to cleaned rids
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On: 1027496
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 00:10 UTC by Nathan Kinder
Modified: 2020-09-13 20:49 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.3.1.6-9.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1027496
Environment:
Last Closed: 2014-06-13 12:32:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 922 0 None None None 2020-09-13 20:49:49 UTC

Description Nathan Kinder 2013-11-07 00:10:30 UTC 
+++ 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.
Comment 1 Rich Megginson 2013-11-11 23:06:32 UTC 
------------------------------------------------------------------------
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 3 Sankar 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
> 
> ------------------------------------------------------------------------
Comment 4 Rich Megginson 2014-01-30 15:33:17 UTC 
(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()
Comment 5 Amita Sharma 2014-02-05 13:19:52 UTC 
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.
Comment 6 Jenny Severance 2014-02-10 15:29:49 UTC 
Amita could you please add the version of 389-ds-base the bug was verified against?
Comment 7 Amita Sharma 2014-02-11 06:05:50 UTC 
Hi Jenny,

Version = 389-ds-base-1.3.1.6-18.el7.x86_64
Report = http://ibm-x3650m4-02-vm-02.lab.eng.bos.redhat.com/qa/archive/beaker/RHEL-7.0-20140127.0/x86_64/389-ds-base-1.3.1.6-18.el7.x86_64/Linux/20140204-000655.html

Thanks,
Ami
Comment 8 Ludek Smid 2014-06-13 12:32:08 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.
Note You need to log in before you can comment on or make changes to this bug.