389-ds-base

#47534 RUV tombstone search with scope "one" doesn`t work
Closed: wontfix Opened by nhosoi.

Closed: wontfix
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1012942

Description of problem:
Replication monitor searches for RUV tombstone entries to get values such as
maxCSN. These searches fail to return any entries and replication monitor
generates empty report.
When line 368 of repl-monitor.pl
    $ruv = $conn->search($replicaroot, "one",
"(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectClass=nsTombstone))",
         0, qw(nsds50ruv nsruvReplicaLastModified));
is changed to
    $ruv = $conn->search($replicaroot, "sub",
"(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectClass=nsTombstone))",
         0, qw(nsds50ruv nsruvReplicaLastModified));
replication monitor generates full report. Indeed search
[root@hp-dl380pgen8-02-vm-1 BE_0]# ldapsearch ... -b "o=my_suffix.com"
"(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectClass=nsTombstone))"
-s one
returns no entries, while
[root@hp-dl380pgen8-02-vm-1 BE_0]# ldapsearch ... -b "o=my_suffix.com"
"(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectClass=nsTombstone))"
-s sub
returns tombstone entries with RUV information.
Version-Release number of selected component (if applicable):
389-ds-base-1.2.11.15-24.el6.x86_64
Additional info:
Possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=788731 .

Bug description: slapi_sdn_scope_test_ext examines the given dn
satisfies the scope against the base dn. Onelevel case for the
tombstone DN ignores the nsuniqueid leaf rdn before checking the
scope which should not be done for the RUV tombstone.

Fix description: This patch correctly handles the RUV tombstone
as an exception.

git patch file (389-ds-base-1.2.11 branch)
0001-Ticket-47534-RUV-tombstone-search-with-scope-one-doe.patch

Thank you for reviewing the patch, Rich!

Pushed to 389-ds-base-1.2.11:
f944cd0..fbece32 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit fbece32d94515bc1ca3889c3d7c0691bbeec3ab0

Pushed to 389-ds-base-1.3.1:
eba7764..a8795a9 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit a8795a928511321f3b46461680cfbf8314edc982

Pushed to master:
92ac8f4..70ed005 master -> master
commit 70ed005088448c22cd3d65c860f0eaeccc6d2619

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.2.11.23

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/871

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
Metadata
None
None
None
Normal
Community
ack
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.