Univention Bugzilla – Bug 34266
UDM uses cn=univention for moving objects
Last modified: 2014-04-22 11:06:03 CEST
Created attachment 5816 [details]
don't use cn=univention for moving objects
We move the temporary objects to cn=univention. This will be ignored by the S4 connector and the S4 connector does not recognize the move.
+++ This bug was initially created as a clone of Bug #33482 +++
I've creates ou=users,ou=MSWATT,<base> containing some users and an empty ou=NoWatt,<base>. With RSAT tools I moved ou=users,ou=MSWATT,<base> to ou=NoWatt,<base>:
20.11.2013 10:45:05,663 LDAP (PROCESS): sync to ucs: [ ou] [ move] OU=users,ou=nowatt,dc=testing,dc=tim
20.11.2013 10:45:05,737 LDAP (ERROR ): Unknown Exception during sync_to_ucs
20.11.2013 10:45:05,759 LDAP (ERROR ): Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1306, in sync_to_ucs
result = self.move_in_ucs(property_type, object, module, position)
File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1196, in move_in_ucs
File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 396, in move
File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 358, in move
raise univention.admin.uexceptions.ldapError, _('Moving not possible: old and new DN are identical.')
ldapError: Moving not possible: old and new DN are identical.
Fixed with r49367. YAML r49368
(In reply to Stefan Gohmann from comment #1)
> Fixed with r49367. YAML r49368
Unable to reproduce the bug, but the description sounds reasonable and the fix does not break anything.
YAML slightly updated.