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 1456769

Summary: ipaAnchorUUID index incorrectly configured and then not indexed
Product: Red Hat Enterprise Linux 7 Reporter: Martin Bašti <mbasti>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Mohammad Rizwan <myusuf>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: ksiddiqu, mbasti, pvoborni, rcritten, tscherf
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.5.0-15.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 09:51:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
console logs none

Description Martin Bašti 2017-05-30 10:31:51 UTC 
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/6975

Detection of the bug: configuration invalid and indexed search fails

check that the index configuration of ipaAnchorUUID is invalid


    ldapsearch -LLL -h localhost -p 389 -D "cn=directory manager" -w xxxxx -b "cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
    dn: cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
    cn: ipaOriginalUid      <<< buggy value
    cn: ipaAnchorUUID
    nsIndexType: eq
    nsIndexType: pres
    nsSystemIndex: false
    objectClass: top
    objectClass: nsIndex


Verify it is not working --> **'notes=U'**


    ldapsearch -LLL -h localhost -p 389 -D "cn=directory manager" -w xxxxx -b "<suffix>" "(ipaAnchorUUID=*)" dn
    [24/May/2017:16:31:53.392012887 +0200] conn=27 op=1 SRCH base="<suffix>" scope=2 filter="(ipaAnchorUUID=*)" attrs="distinguishedName"
    [24/May/2017:16:31:53.430503561 +0200] conn=27 op=1 RESULT err=0 tag=101 nentries=0 etime=0 notes=U


Workaround is to fix the config and reindex

fix the configuration


    ldapmodify -h localhost -p 389 -D "cn=directory manager" -w xxxxx
    dn: cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
    changetype: modify
    delete: cn
    cn: ipaOriginalUid
    
    ldapsearch -LLL -h localhost -p 389 -D "cn=directory manager" -w xxxxx -b "cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
    dn: cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
    cn: ipaAnchorUUID
    nsIndexType: eq
    nsIndexType: pres
    nsSystemIndex: false
    objectClass: top
    objectClass: nsIndex


reindex ipaAnchorUUID


    ipactl stop
    db2index -Z TEST-COM -n userRoot -s "<suffix>" -t ipaAnchorUUID
    ipactl start


Check workaround worked


    ldapsearch -LLL -h localhost -p 389 -D "cn=directory manager" -w xxxxx -b "<suffix>" "(ipaAnchorUUID=*)" dn
    [24/May/2017:16:41:08.779602212 +0200] conn=26 op=1 SRCH base="<suffix>" scope=2 filter="(ipaAnchorUUID=*)" attrs="distinguishedName"
    [24/May/2017:16:41:08.785696976 +0200] conn=26 op=1 RESULT err=0 tag=101 nentries=0 etime=0
Comment 2 Martin Bašti 2017-05-30 10:33:05 UTC 
Fixed upstream
master:
https://pagure.io/freeipa/c/49ce395b90ea64eda3f9362b05936a3e4d43234a
ipa-4-5:
https://pagure.io/freeipa/c/8410823e1811ac9e004cc79556334abd429d480d
Comment 5 Mohammad Rizwan 2017-06-08 11:00:41 UTC 
Can we have steps for verification for this bug?
Comment 6 Martin Bašti 2017-06-08 12:30:32 UTC 
Use ldapsearch 

ldapsearch -LLL -h localhost -p 389 -D "cn=directory manager" -w Secret123 "(ipaAnchorUUID=*)"

and check /var/log/dirsrv/slapd-*/access log. There shouldn't be "notes=U" in log entry of that search
Comment 7 Martin Bašti 2017-06-08 12:40:04 UTC 
or you can check

ldapsearch -LLL -h localhost -p 389 -D "cn=directory manager" -w Secret123 -b "cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config

if contains exactly

dn: cn=ipaAnchorUUID,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
cn: ipaAnchorUUID
nsIndexType: eq
nsIndexType: pres
nsSystemIndex: false
objectClass: top
objectClass: nsIndex
Comment 8 Mohammad Rizwan 2017-06-09 06:10:54 UTC 
Created attachment 1286304 [details]
console logs
Comment 9 Mohammad Rizwan 2017-06-09 06:11:38 UTC 
Verified using steps provided in comment #6 and #7.

version:
ipa-server-4.5.0-16.el7.x86_64
 
console logs are attached.
Comment 10 errata-xmlrpc 2017-08-01 09:51:24 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://access.redhat.com/errata/RHBA-2017:2304