Bug 46068 – use univention-ldapsearch in univention-check-join-status instead of simple ldapsearch

Bug 46068 - use univention-ldapsearch in univention-check-join-status instead of simple ldapsearch


Summary:	use univention-ldapsearch in univention-check-join-status instead of simple l...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Join (univention-join)
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-01-17 16:40 CET by Felix Botner
Modified:	2022-12-08 17:49 CET (History)
CC List:	2 users (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):	bitesize, Error handling
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 Felix Botner

2018-01-17 16:40:38 CET

use univention-ldapsearch in univention-check-join-status instead of simple ldapsearch to be more robust ...

our app test sometimes fail, because at some point univention-check-join-status is called to check if the system is OK, but at the same time the slapd is restarted and immediately fails (because of ldapsearch) and so the test

univention-ldapsearch has some retry functionality, so we should use this in univention-check-join-status

Comment 1 Felix Botner

2018-01-23 09:55:13 CET

for now, i tried to make assert_join more robust

utils/utils.sh assert_join 5bc44bcfad2f3fe880100840d1dba48495bf2265 (4.3)
try univention-check-join-status three times

if that works, i merge it to 4.2-3