Description Arvid Requate 2013-05-22 15:05:04 CEST

During tests for UCS@school 3.1-R2 a huge number of temporary
SID-lock objects for user accounts were found under cn=sid,cn=temporary,cn=univention. It looks like user creation was interrupted during the import of one of the users and all subsequent sid allocations according to the default algorithm then failed in the first attempt, leaving sid locks for all sids tried:


root@master:~# univention-ldapsearch -xLLL uidnumber=5005 sambasid
dn: uid=otto58,cn=schueler,cn=users,ou=gsmitte,dc=nstx,dc=local
sambaSID: S-1-5-21-2257737218-4041955148-3984386485-11010

## next something happened, preventing assignement of 11012:
## Note: there is lock cn=S-1-5-21-2257737218-4041955148-3984386485-11012

root@master:~# univention-ldapsearch -xLLL uidnumber=5006 sambasid
dn: uid=otto59,cn=schueler,cn=users,ou=gsmitte,dc=nstx,dc=local
sambaSID: S-1-5-21-2257737218-4041955148-3984386485-11014

## to cut a long story short, this happes for all users created subsequently:

root@master:~# univention-ldapsearch -xLLL uidnumber=25900 sambasid
dn: uid=ulrike511,cn=schueler,cn=users,ou=gsmitte,dc=nstx,dc=local
sambaSID: S-1-5-21-2257737218-4041955148-3984386485-52802


## In the end there were about 20896 sid lock objects.


+++ This bug was initially created as a clone of Bug #31389 +++