Bug 57596 - 52_s4connector/199sync_ucs_case_only_rename_ou fails -- is temporary_move_container still required?
Summary: 52_s4connector/199sync_ucs_case_only_rename_ou fails -- is temporary_move_co...
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact: UMC maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-11 15:23 CEST by Arvid Requate
Modified: 2024-09-11 15:23 CEST (History)
0 users

See Also:
What kind of report is it?: Development Internal
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:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
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 Arvid Requate univentionstaff 2024-09-11 15:23:20 CEST 
When renaming containers or OUs in UDM the module code uses a workaround and creates a "temporary_move_container_[...]". This is "pretty interesting" for the S4-Connector and AD-Connector. Currently the "52_s4connector/199sync_ucs_case_only_rename_ou" test fails, which should prove that the S4-Connector can handle this.

Maybe we should check if that workaround with "temporary_move_container" is still needed. At least with UCS 5.0-8 with a slapd with lmdb backend I can rename a OU simply with modrdn:

eval "$(ucr shell ldap/base)"
udm container/ou create --set name=edgwcwrvAAA
udm users/user create \
    --position=ou=edgwcwrvAAA,"$ldap_base" \
    --set username=foo1 --set lastname=name1 --set password=univention
ldapmodrdn \
    -D cn=admin,"$ldap_base" -y /etc/ldap.secret \
    -r ou=edgwcwrvAAA,"$ldap_base" ou=edgwcwrvaaa