Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1601470 - Unable to read the RUV after a db2index operation.
Summary: Unable to read the RUV after a db2index operation.
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.7-Alt
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 7.7
Assignee: Ludwig
QA Contact: RHDS QE
Depends On:
TreeView+ depends on / blocked
Reported: 2018-07-16 13:04 UTC by German Parente
Modified: 2019-03-19 14:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description German Parente 2018-07-16 13:04:41 UTC
Description of problem:

in ipa context, if we do a 

db2index -n changelog

there's not only changelog that is re-indexed but all the backends.

Also, there's a backup that is being performed.

And after that, as a consequence, we cannot read the RUV anymore with a command like this:

ldapsearch -D "cn=directory manager" -W -b <root suffix> '(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectclass=nstombstone))'

Version-Release number of selected component (if applicable): 389-ds-base- (but shown in other versions)

Comment 3 Ludwig 2018-12-05 17:15:10 UTC
reproduced the failure to get the ruv object after a db2index -n changelog

the fffffff-ffffff-ffffff-fffffff entzyr is in the id2entry and in the objectclass and nsuniqueid index, but not returned.

The strange thing is that we do not normally return the entry itself but the in memory ruv in the cn=replica entry. 
Need to check why this mapping now fails.

Comment 4 Ludwig 2018-12-05 17:29:38 UTC
it is the entryrdn index that gets corrupted.

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