#49801 Add different DEBUGGING levels
Closed: wontfix by spichugi. Opened by vashirov.

Issue Description

When running tests with DEBUGGING variable set, output is very noisy. It would be nice to control what kind of debug output we want to get. For example, enabling audit/auditfail logging, setting error logging to a desired level (replication, aci, etc.) during/after instance creation.

Another issue is that with DEBUGGING instances at the end of a test are automatically stopped. This is not always a desired state, sometimes we need instance to keep running after running the test.

Package Version and Platform

1.4.x

Steps to reproduce

  1. DEBUGGING=True py.test test_name.py

Actual results

A lot of debugging messages are printed, instances are stopped.

Expected results

DEBUGGING should allow fine grained control over debug levels and the desired state of the instances.


Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4.0
- Issue tagged with: lib389

Metadata Update from @vashirov:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4 (was: 1.4.0)

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 issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2860

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

Metadata