Bug 33430 - pTRRecord not indexed
pTRRecord not indexed
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-0-errata
Assigned To: Arvid Requate
Janek Walkenhorst
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-15 16:57 CET by Erik Damrose
Modified: 2014-01-29 11:19 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2013-11-15 16:57:37 CET
Despite being present univention-ldap-server.postinst, pTRRecord is logged as not indexed:

Nov 15 16:40:59 backup slapd[17609]: conn=1098 op=23 SRCH base="cn=shares,dc=ucsqapt,dc=local" scope=1 deref=0 filter="(&(objectClass=dNSZone)(!(relativeDomainName=@))(|(zoneName=*.in-addr.arpa)(zoneName=*.ip6.arpa))(|(pTRRecord=l*)(relativeDomainName=l*)))"
Nov 15 16:40:59 backup slapd[17609]: <= bdb_substring_candidates: (pTRRecord) not indexed

Attributes were tested by using Felix' script from Bug 29509#c7
Comment 1 Arvid Requate univentionstaff 2013-12-19 15:22:29 CET
There were a few possible index type combinations missing. As a consequence, some attributes where not indexed for all search types they were configured for by UCR. This affected the following attributes:

* name (now also indexed for presence)
* pTRRecord and sambaSID (now also indexed for substring)

Advisory: 2013-12-19-univention-ldap.yaml
Comment 2 Janek Walkenhorst univentionstaff 2014-01-24 17:39:03 CET
(In reply to Arvid Requate from comment #1)
> There were a few possible index type combinations missing. As a consequence,
> some attributes where not indexed for all search types they were configured
> for by UCR.
All index combinations are now correctly configured.

Advisory: OK
Comment 3 Moritz Muehlenhoff univentionstaff 2014-01-29 11:19:03 CET
http://errata.univention.de/ucs/3.2/37.html