Bug 31414 - UDM temporary sid alloc lock objects still present after successful machine account creation
UDM temporary sid alloc lock objects still present after successful machine a...
Status: RESOLVED DUPLICATE of bug 41711
Product: UCS
Classification: Unclassified
Component: UMC - Computers
UCS 3.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-22 14:34 CEST by Arvid Requate
Modified: 2018-04-13 13:29 CEST (History)
4 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2013-05-22 14:34:46 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 +++
Comment 1 Florian Best univentionstaff 2016-06-29 17:30:42 CEST
*** Bug 28632 has been marked as a duplicate of this bug. ***
Comment 2 Florian Best univentionstaff 2016-06-30 17:00:04 CEST

*** This bug has been marked as a duplicate of bug 41711 ***