Univention Bugzilla – Bug 31414
UDM temporary sid alloc lock objects still present after successful machine account creation
Last modified: 2018-04-13 13:29:38 CEST
During tests for UCS@school 3.1-R2 it was discovered that the temporary SID-lock objects for machine accounts are not removed after a machine account was created successfully. In this case cn=sid,cn=temporary,cn=univention contained lock objects for all the hosts created/joined into the system: master, slave, slavev, dcfoo-01, dcfoov-01, winxp-32bit, winxp-64bit, win7-32bit, win7-64bit, win8-32bit, win8-64bit, win7-120, win7-121, winxp-122, winxp-123 Probably the lock object should be cleaned up after successful creation (via allocators.confirm() ?) +++ This bug was initially created as a clone of Bug #31389 +++
*** Bug 28632 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 41711 ***