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 1601470 - Unable to read the RUV after a db2index operation.
Summary: Unable to read the RUV after a db2index operation.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-16 13:04 UTC by German Parente
Modified: 2022-05-10 14:11 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 13:43:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3162 0 None open Unable to read the RUV after a db2index operation 2020-10-23 08:52:49 UTC
Red Hat Issue Tracker IDMDS-1755 0 None None None 2021-11-02 15:34:31 UTC
Red Hat Product Errata RHBA-2022:1815 0 None None None 2022-05-10 13:43:29 UTC

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


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