Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1237325

Summary: reindex off-line twice could provoke index corruption
Product: Red Hat Enterprise Linux 7 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: nkinder, rmeggins, vashirov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.4.0-3.el7 Doc Type: Bug Fix
Doc Text:
Cause: When nsMatchingRule was dynamically updated in an index entry, the value was set to the configuration but was not applied to the attribute info. Consequence: dbverify utility was confused by the inconsistent settings and reported the db corruption although it was not. Fix: The nsMatchingRule change is properly applied to the attribute info. Result: dbverify utility reports the correct db status.
 Story Points: ---
Clone Of: 1236656 Environment:
Last Closed: 2015-11-19 11:42:49 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:
Bug Depends On: 1236656    
Bug Blocks:    

Comment 2 Viktor Ashirov 2015-07-14 13:17:38 UTC 
Build tested: 389-ds-base-1.3.4.0-5.el7.x86_64

I performed manual verification with steps from https://bugzilla.redhat.com/show_bug.cgi?id=1236656#c0

[root@rhel7ds ~]# /usr/lib64/dirsrv/slapd-rhel7ds/dbverify 
DB verify: Passed

Automated test passed as well after I increased wait timeout for reindexUidNumber to finish. 

============================================================================ test session starts =============================================================================
platform linux2 -- Python 2.7.5 -- py-1.4.30 -- pytest-2.7.2 -- /usr/bin/python
rootdir: /tmp/test/ds/dirsrvtests/tickets, inifile: 
collected 2 items 

test/ds/dirsrvtests/tickets/ticket48212_test.py::test_ticket48212_run PASSED
test/ds/dirsrvtests/tickets/ticket48212_test.py::test_ticket48212_final PASSED

========================================================================= 2 passed in 94.05 seconds ==========================================================================

Marking as VERIFIED.
Comment 3 errata-xmlrpc 2015-11-19 11:42:49 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, 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://rhn.redhat.com/errata/RHBA-2015-2351.html