Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 788731 - ruv tombstone searches don't work after reindex entryrdn
ruv tombstone searches don't work after reindex entryrdn
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
IDM QE LIST
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-08 17:03 EST by Rich Megginson
Modified: 2012-06-20 03:14 EDT (History)
4 users (show)

See Also:
Fixed In Version: 389-ds-base-1.2.10.0-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Attempt to search for the RUV tombstone entry (as is done by client such as repl-monitor). Consequence: The entry is not found. Fix: Correctly index this entry in the entryrdn index. Result: Searches for RUV tombstone entries work correctly.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 03:14:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0813 normal SHIPPED_LIVE Low: 389-ds-base security, bug fix, and enhancement update 2012-06-19 15:29:15 EDT

  None (edit)
Description Rich Megginson 2012-02-08 17:03:50 EST
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/273

setup replication with 1.2.10.a6 or earlier - verify replication is working

upgrade to 1.2.10.a8

do a search like this:

ldapsearch -xLLL -D "cn=directory manager" -w password -b dc=example,dc=com '(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectclass=nstombstone))'

You will see no entries returned.  The entryrdn.db4 looks like this:

 dc=example,dc=com
  ID: 1; RDN: "dc=example,dc=com"; NRDN: "dc=example,dc=com"
 nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff
  ID: 10; RDN: "nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff"; NRDN: "nsunique
id=ffffffff-ffffffff-ffffffff-ffffffff"

That is, it thinks the ruv tombstone rdn is a suffix instead of a child of dc=example,dc=com
Comment 2 Jenny Galipeau 2012-02-20 10:03:42 EST
Steps to reproduce with RHDS needed.
Comment 4 Noriko Hosoi 2012-05-11 14:40:32 EDT
Adding a test case to tet.
Comment 5 Noriko Hosoi 2012-05-14 17:39:51 EDT
It's already there (in mmrepl/accept.sh bug788729 :p).
Comment 6 Rich Megginson 2012-05-24 19:32:16 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Attempt to search for the RUV tombstone entry (as is done by client such as repl-monitor).
Consequence: The entry is not found.
Fix: Correctly index this entry in the entryrdn index.
Result: Searches for RUV tombstone entries work correctly.
Comment 7 Amita Sharma 2012-05-29 07:29:28 EDT
mmrepl mmraccept startup 	100% (2/2) 	  	 
mmrepl mmraccept run 	100% (23/23) 	  	 
mmrepl mmraccept cleanup 	100% (1/1)
Hence marking as VERIFIED.
Comment 8 errata-xmlrpc 2012-06-20 03:14:03 EDT
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.

http://rhn.redhat.com/errata/RHSA-2012-0813.html

Note You need to log in before you can comment on or make changes to this bug.