Bug 37516 – ucs_unregisterLDAPExtension should implement a wait for ldap-restart

Bug 37516 - ucs_unregisterLDAPExtension should implement a wait for ldap-restart


Summary:	ucs_unregisterLDAPExtension should implement a wait for ldap-restart

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	LDAP
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-01-12 11:34 CET by Ammar Najjar
Modified:	2018-04-14 13:43 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ammar Najjar

2015-01-12 11:34:36 CET

When calling the function "ucs_unregisterLDAPExtension" from the script "/usr/share/univention-lib/ldap.sh" there is no indication regarding restarting the ldap server, which is necessary for any further operations on ldap objects where the changes occur for they might hit an already removed object meanwhile the ldap server has not finished restarting yet.

So it should be in the order:
ucs_unregisterLDAPExtension (include ldap restart) -> wait for ldap to finish restarting -> exit  to allow operations on ldap objects (e.g: modify.. )

Currently this causes timing issue for bug #37401, where a sleep statement is used temporarily in script "10_ldap.80acl_unregistration_basis" to make sure that the ldap server finished restarting, please remove that statement when this bug is fixed.