Bug 48674 - Improve wait_for_s4connector
Summary: Improve wait_for_s4connector
Status: RESOLVED DUPLICATE of bug 49415
Alias: None
Product: UCS Test
Classification: Unclassified
Component: S4 Connector
Version: unspecified
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Jürn Brodersen
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-14 10:34 CET by Jürn Brodersen
Modified: 2019-07-02 14:29 CEST (History)
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):
Customer ID:
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 Jürn Brodersen univentionstaff 2019-02-14 10:34:01 CET 
Improve wait_for_s4connector

wait_for_s4connector currently waits for at least a minute. I think that much time is not needed.

Also no timeout exists.
Comment 1 Florian Best univentionstaff 2019-05-03 13:52:30 CEST 
Which wait_for_s4connector() implementation are you refering to?

univention.testing.ucs_samba.wait_for_s4connector() waits only the specified timeout.

In tests/52_s4connector/100sync_gpo_ntsecurity_descriptor the function wait_for_s4connector_sync_to_ucs() waits ~2 minutes.
Comment 2 Florian Best univentionstaff 2019-05-03 14:39:16 CEST 
You already commited:

ucs-test (9.0.0-28)
ec6b78308e9a | Bug #48674: Add timeout for wait_for_s4connector
Comment 3 Jürn Brodersen univentionstaff 2019-07-02 14:29:47 CEST 

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