Maybe I miss something but it looks a bit odd to me.

You say in the steps: Operations should be successful, but you skip all exceptions here... So, in my opinion, either the expectedresults step should be more accurate or we should have better defined try-except as here...

I think this needs a test skip if systemd == false/0, because this may not work in containers.

Maybe I miss something but it looks a bit odd to me.
You say in the steps: Operations should be successful, but you skip all exceptions here... So, in my opinion, either the expectedresults step should be more accurate or we should have better defined try-except as here...

This was a reproducer, not a proper test, there is no recovery step after the deadlock (i.e. the server will hang and instance removal might fail).
I'll update this test case to handle err=68 and add a proper cleanup.

I think this needs a test skip if systemd == false/0, because this may not work in containers.

Yes, I will add it, thanks.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3875

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.