Univention Bugzilla – Bug 37709
rename operation failed during sync from ucs: [windowscomputer]
Last modified: 2015-08-06 17:52:33 CEST
+++ 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"
* 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
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.
<http://errata.univention.de/ucs/4.0/275.html>