conflict_resolve_test.py fails in debugging mode

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50383

• Created at 2019-05-16 16:33:55 by vashirov (@vashirov)
• Assigned to nobody

---

Issue Description

Not sure why, but conflict_resolve_test.py fails only with DEBUGGING=True:

dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_add_modrdn PASSED                                       [ 16%]
dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_complex_add_modify_modrdn_delete ERROR                  [ 33%]
dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_memberof_groups ERROR                                   [ 50%]
dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_managed_entries xfail                                   [ 66%]
dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_nested_entries_with_children ERROR                      [ 83%]
dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestThreeMasters::test_nested_entries xfail                                  [100%]

Opening this for the further investigation.

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-05-16 17:56:49

Metadata Update from @mreynolds389:

• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Issue set to the milestone: 1.4.1

[389-ds-bot]

Comment from vashirov (@vashirov) at 2020-02-12 18:00:03

Metadata Update from @vashirov:

• Issue set to the milestone: CI test 1.0 (was: 1.4.1)