Bug 58780 - Renaming a parent ou causes duplicates if children are renamed [5.2]
Summary: Renaming a parent ou causes duplicates if children are renamed [5.2]
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: AD Connector
Version: UCS 5.2
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 5.2-3-errata
Assignee: Samba maintainers
QA Contact: Samba maintainers
URL:
Keywords:
Depends on: 58739
Blocks:
  Show dependency treegraph
 
Reported: 2025-11-04 16:59 CET by Arvid Requate
Modified: 2025-11-05 19:07 CET (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 4: A User would return the product
User Pain: 0.160
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
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 2025-11-04 16:59:47 CET
We should also port this fix form 5.0-10 to 5.2-3

+++ This bug was initially created as a clone of Bug #58739 +++

Renaming a parent ou causes duplicates if children are renamed

How to reproduce (all renames are in AD, with read only connector):

Add ou1
Add ou1,ou1.1
Add ou1,ou1.1,ou1.1.1
Rename ou1,ou1.1->ou1,ou1.2
Rename ou1,ou1.2,ou1.1.1->ou1,ou1.2,ou1.2.1
Check ucs ldap -> You should now have ou1,ou1.2,ou1.1.1 and ou1,ou1.2,ou1.2.1
If you rename a user in ou1,ou1.2,ou1.2.1 (which was created in ou1,ou1.1,ou1.1.1) it will be "duplicated" into ou1,ou1.2,ou1.2.1 (the user was never moved in UCS and is exists in ou1,ou1.2,ou1.1.1)