Open wladich opened 3 years ago
@tbordaz Could you please look at the backtrace? Do you need any additional data to investigate the issue? I can reproduce the issue by running the test on local vagrant environment, but it PR-CI the it is passing succesfuly.
The test which triggers the issue: https://github.com/wladich/freeipa/blob/d3e6734c3f731df53764a14c3dee009fb23478f1/ipatests/test_integration/test_global_catalog.py#L565 http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/dbd7866a-17cf-11eb-be89-fa163e4ad552/report.html
Just hit the issue again, here is what the test is doing:
systemctl stop ipa-gcsyncd.service
ipa user-add StartupsyncComplex1 --first Startupsync --last Complex1
ipa user-add StartupsyncComplex2 --first Startupsync --last Complex2
ipa user-del StartupsyncComplex1
ipa group-add startupsynccomplex
ipa group-add-member startupsynccomplex --users StartupsyncComplex2
systemctl start ipa-gcsyncd.service
And ipa-gcsyncd fails to start, the traceback can be seen in the first comment
After a test session I can not start sync daemon anymore. I am not sure which action triggered the error so I am attaching output of
ldapsearch
for main and GC instancesAnother issue I see is that the traceback is written only to journal but not to
globalcatalog.log
.