Univention Bugzilla – Bug 50108
UCS@school: Allow re-creation of deleted user object with same objectSid in Samba/AD
Last modified: 2021-08-30 17:53:53 CEST
In a school customer environment on two different school slaves just like in Bug 49792 with the deleted groups, here a deleted user could not be "reanimated". I could do it just like in the other Bug manually to fix the reject. Here is how the reject looks like: --------------------------------------------------------------------------------------------------------------------------------------------------------- 01.09.2019 06:26:14.262 LDAP (PROCESS): __sync_file_from_ucs: Object with entryUUID e9af84a0-0cce-1039-9f8b-dd06351c30bf has been removed before but became visible again. 01.09.2019 06:26:14.270 LDAP (PROCESS): sync from ucs: [ user] [ add] cn=lara.craft,cn=mitarbeiter,cn=users,ou=sun,DC=schein,DC=me 01.09.2019 06:26:15.151 LDAP (ERROR ): sync_from_ucs: traceback during add object: cn=lara.craft,cn=mitarbeiter,cn=users,ou=sun,DC=schein,DC=me 01.09.2019 06:26:15.151 LDAP (ERROR ): sync_from_ucs: traceback due to addlist: [('objectClass', ['top', 'user', 'person', 'organizationalPerson']), ('sAMAccountName', [u'lara.craft']), ('objectSid', ['\x01\x05\x00\x00\x00\x00\x00\x05\x15\x00\x00\x00\x15\x10U\xf2!\\\xeco\xa1\xecO7\xe8\x14\x01\x00']), (u'sn', [u'Craft']), (u'displayName', [u'Lara Craft']), (u'givenName', [u'Lara']), ('primaryGroupID', ['11819'])] 01.09.2019 06:26:15.154 LDAP (WARNING): sync failed, saved as rejected /var/lib/univention-connector/s4/1564486798.934798 01.09.2019 06:26:15.186 LDAP (WARNING): Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/univention/s4connector/__init__.py", line 897, in __sync_file_from_ucs if ((old_dn and not self.sync_from_ucs(key, mapped_object, pre_mapped_ucs_dn, unicode(old_dn, 'utf8'), old, new)) or (not old_dn and not self.sync_from_ucs(key, mapped_object, pre_mapped_ucs_dn, old_dn, old, new))): File "/usr/lib/python2.7/dist-packages/univention/s4connector/s4/__init__.py", line 2412, in sync_from_ucs self.lo_s4.lo.add_ext_s(compatible_modstring(object['dn']), compatible_addlist(addlist), serverctrls=ctrls) # FIXME encoding File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 195, in add_ext_s resp_type, resp_data, resp_msgid, resp_ctrls = self.result3(msgid,all=1,timeout=self.timeout) File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 514, in result3 resp_ctrl_classes=resp_ctrl_classes File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 521, in result4 ldap_result = self._ldap_call(self._l.result4,msgid,all,timeout,add_ctrls,add_intermediates,add_extop) File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 106, in _ldap_call result = func(*args,**kwargs) CONSTRAINT_VIOLATION: {'info': '0000202F: ../../ldb_key_value/ldb_kv_index.c:2506: Failed to re-index objectSid in CN=lara.craft,CN=mitarbeiter,CN=users,OU=sun,DC=schein,DC=me - ../../ldb_key_value/ldb_kv_index.c:2351: unique index violation on objectSid in CN=lara.craft,CN=mitarbeiter,CN=users,OU=sun,DC=schein,DC=me', 'desc': 'Constraint violation'} -------------------------------------------------------------------------------------------------------------------------------------------
The patch from Bug 49792 should fix this too.
(In reply to Arvid Requate from comment #1) > The patch from Bug 49792 should fix this too. So it's a duplicate of that bug then?