Bug 47345 - Improve wait_for_drs_replication and add to some test
Improve wait_for_drs_replication and add to some test
Status: RESOLVED DUPLICATE of bug 49415
Product: UCS Test
Classification: Unclassified
Component: Framework
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Jürn Brodersen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-11 20:40 CEST 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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürn Brodersen univentionstaff 2018-07-11 20:40:23 CEST
The base keyword argument is always overwritten.
Throw an exception in case a timeout occurred.
Comment 1 Jürn Brodersen univentionstaff 2018-07-12 17:24:38 CEST
Add to
07_container_ou_rename_uppercase_with_special_characters
07_container_ou_rename_uppercase
Comment 2 Florian Best univentionstaff 2019-05-03 14:34:38 CEST
You already commited:

ucs-test (8.0.28-148)
23666b28b4d0 | Bug #47345: Improve wait_for_drs_replication

ucs-test (8.0.28-150)
b6427c02291c | Bug #47345: Wait for s4 replication for containers

ucs-test (8.0.28-149)
7b6c43ca2bba | Bug #47345: ldap users are not replicated to s4 -> do not wait

ucs-test (8.0.28-151)
9fb4d275be9b | Bug #47345: Wait for s4 replication for containers (2)

ucs-test (9.0.2-38)
aae64220e97c | Bug #47345: add wait_for_drs_replication to udm test cleanup

ucs-test (9.0.2-41)
2c5feff1d7e4 | Bug #47345: only call wait_for_drs_replication if udm deletion succeeded
Comment 3 Florian Best univentionstaff 2019-05-03 14:34:58 CEST
I improoved this in Bug #49415.
Comment 4 Jürn Brodersen univentionstaff 2019-07-02 14:29:37 CEST

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