Bug 1601470

Summary:	Unable to read the RUV after a db2index operation.
Product:	Red Hat Enterprise Linux 8	Reporter:	German Parente <gparente>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	8.1	CC:	cpelland, gkimetto, mreynolds, nkinder, pasik, pcech, sgouvern, spichugi, tbordaz, tmihinto, vashirov
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 13:43:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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-1.3.7.5-19.el7_5.x86_64 (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.

Comment 11 mreynolds 2021-10-28 16:02:12 UTC

This appears to be fixed via:  

https://github.com/389ds/389-ds-base/issues/4910

Comment 17 errata-xmlrpc 2022-05-10 13:43:00 UTC

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 (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1815