Bug 48835 – mdb_equality_candidates ... not indexed messages after 4.3.3-448

Bug 48835 - mdb_equality_candidates ... not indexed messages after 4.3.3-448


Summary:	mdb_equality_candidates ... not indexed messages after 4.3.3-448

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:	https://unix.stackexchange.com/questi...
Keywords:

Depends on:
Blocks:	53709
	Show dependency tree / graph

Reported:	2019-03-01 20:20 CET by Dirk Ahrnke
Modified:	2021-08-27 11:38 CEST (History)
CC List:	6 users (show)

See Also:	48970 39866
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Dirk Ahrnke 2019-03-01 20:20:54 CET

I have noticed the new occurence of "mdb_equality_candidates: (attribute) not indexed" on two systems after applying the upgrades to errata 448.
In my case the attributes were "kopanoAccount" and "ownCloudEnabled|nextcloudEnabled". Other attributes may be affected too.

On one machine I could proove that the UCRV "ldap/index/eq" included the attributes in question before the upgrade and missed them afterwards. Without checking the code I would conclude that some routine has reset the UCRV to a default. This assumption can be confirmed by checking config-registry.replog

The solution described in https://help.univention.com/t/problem-log-entries-mdb-equality-candidates-o-not-indexed/10259 will fix the problem.

Comment 1 Dirk Ahrnke 2019-03-13 14:31:34 CET

most likely solved by #48970

Comment 2 Florian Best

2019-03-13 14:41:18 CET

(In reply to Dirk Ahrnke from comment #1)
> most likely solved by #48970

Ahh, makes sense! I will mark as duplicate.

*** This bug has been marked as a duplicate of bug 48970 ***

Comment 3 Arvid Requate

2019-03-13 18:39:11 CET

The fix for Bug 48970 does two things:

* prevents that additional systems run into this issue
* restores UCS@school specific attribute indices

But it doesn't restore the indices other apps configured.

Comment 4 Arvid Requate

2019-03-13 18:43:29 CET

While releasing the update for Bug 48970 today I had the idea that we could just set the UCR variables the superset of all attributes that apps may have added to the index and then run ldap_setup_index --remove-unknown to strip away the ones that are unknown in that domain. That could be a "one size fits all" solution but requires some testing.

Comment 5 Arvid Requate

2019-03-13 18:44:16 CET

Grepping for "ldap_setup_index" shows two attributes that we index, that might also have been lost: univentionAppID univentionUDMPropertyCopyable

Comment 6 Ingo Steuwer

2021-05-14 16:47:15 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.