Why do you use classes here? I think the functions will be less confusing here.

it is okay to pass UTF-8 here, not bytes. lib389 does all the magic for you

topo.standalone.config.set('nsslapd-disk-monitoring-grace-period', '1')

please, use subprocess module.
Justification
https://docs.python.org/3/library/subprocess.html#subprocess-replacements

The common practice is to use noun for the fixtures:
smtp_connection, setup, test_user

@spichugi all changes are done as suggested by you

Please, don't use 'shell=True'. Use a list of arguments like ['dd', 'if=/dev/zero', etc]
Checkout the Warning (red)
https://docs.python.org/2/library/subprocess.html#frequently-used-arguments

One more class here. The same as previous, you don't need it, it can be a function.

these two lines should be put to 'finally' block of 'try-finally'.
We should make sure that the files are deleted even if the test case failed

Always use the open() function in the https://docs.python.org/3/tutorial/inputoutput.html#reading-and-writing-files

with open() as f:
     # do something

It will close the file anyway in the end.

you can get utf8 with get_attr_val_utf8 and compare with a normal string. It is more humany

I think we dont need the sleep here.
It will make the test execution longer for no reason.
You can either verify using a timeout in loop with time.sleep(1) inside (and break from it when the check is successful) or some other way.

topo.standalone.config.set('nsslapd-disk-monitoring', 'on') - this should woek fine (without 'b')

You can add a test user with 'UserAccounts' here instead of legacy Entry object

Please, remove all of the big sleeps (bigger then time.sleep(1)). And use another approach I describe before (or any other way)

Why do you need it? It looks redundant

we have a topo.standalone.config.remove_all() for that in DSLdapObject

@spichugi all changes done . Please merge if all ok .

Typo :) And this is copied and pasted throughout the script

@mreynolds , typo corrected, :) . Please merge if all ok .

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/3157

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.