Bug 37709

Summary: rename operation failed during sync from ucs: [windowscomputer]
Product: UCS Reporter: Felix Botner <botner>
Component: UDM (Generic)Assignee: Felix Botner <botner>
Status: CLOSED FIXED QA Contact: Arvid Requate <requate>
Severity: normal    
Priority: P5 CC: dev.faz, gohmann, requate, walkenhorst
Version: UCS 3.1   
Target Milestone: UCS 4.0-2-errata   
Hardware: Other   
OS: Linux   
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: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional):
Max CVSS v3 score:
Bug Depends on: 31083    
Bug Blocks:    

Description Felix Botner univentionstaff 2015-02-06 10:19:21 CET 
+++ This bug was initially created as a clone of Bug #31083 +++

The following S4-Connector reject was found in a customer environment:

================================================================
    1:   UCS DN: cn=machine1,cn=computers,ou=school1,$ldap_base
          S4 DN: cn=machine2,cn=computers,ou=school1,$ldap_base
         Filename: /var/lib/univention-connector/s4/1365249382.121660
================================================================

The traceback indicates that the rename failed:

"Modify of RDN 'cn' on cn=machine2,cn=computers,ou=school1,$ldap_base not permitted, must use 'rename' operation instead"
Comment 1 Felix Botner univentionstaff 2015-08-03 19:13:19 CEST 
* merged changes from 3.2-6 to 4.0-2
  r62599
  merged to 4.1

* added tests/52_s4connector/403rename_computer_object to ucs-test
  r62603
  merged to 4.1

* yaml: 2015-08-03-univention-s4-connector.yaml
Comment 2 Arvid Requate univentionstaff 2015-08-06 13:50:18 CEST 
Ok, it works:

* Without the patch I rename a Windows-Client in UDM and get a reject.

* If I do the same with the new univention-s4-connector package, I don't get a reject and the object is also renamed in Samba4.

* Existing rename rejects are not fixed automatically by this patch (this is because the first half of the modrdn is lost/not in the reject list). As a workaround I can rename the client back to it's old name in UMC and then, in a second step I rename him again to the new name. After a bit of waiting the remaining reject then resolves.

* Advisory Ok.
Comment 3 Janek Walkenhorst univentionstaff 2015-08-06 17:52:33 CEST 
<http://errata.univention.de/ucs/4.0/275.html>