Bug 55936 - resync_objects_fom_ucs.py should read from local LDAP by default
resync_objects_fom_ucs.py should read from local LDAP by default
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 5.0
Other Linux
: P5 normal (vote)
: UCS 5.0-4-errata
Assigned To: Felix Botner
Nikola Radovanovic
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-04-03 14:55 CEST by Arvid Requate
Modified: 2023-07-12 13:57 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 1: Will affect a very few 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.057
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023031421000378
Bug group (optional): bitesize
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2023-04-03 14:55:03 CEST
The script resync_objects_fom_ucs.py currently always reads from ldap/master.

To improve performance in UCS@school scenarios, it should read from the local LDAP server by default.
Comment 2 Felix Botner univentionstaff 2023-07-06 14:51:47 CEST
Successful build
Package: univention-ad-connector
Version: 14.0.16-2
Branch: ucs_5.0-0
Scope: errata5.0-4

Successful build
Package: univention-s4-connector
Version: 14.0.15-2
Branch: ucs_5.0-0
Scope: errata5.0-4


univention-ad-connector.yaml
univention-s4-connector.yaml

By default resync_object_from_ucs.py now uses the local LDAP
server for LDAP lookups. Use the option `--from-primary`
for the old behavior (LDAP lookup on primary directory node).