389-ds-base

#49734 Various issues with Disk Monitoring
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

Internal testing has revealed that several parts of the disk monitoring feature are not working correctly. One issue is how it checked if verbose error logging was set, and other issues around shutting down when the disk is full, and removing archived log files.

https://pagure.io/389-ds-base/pull-request/49759

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review
- Custom field type adjusted to None
- Custom field version adjusted to None

commit 1c5831c02c3e052c097f4b19c7d3ddf00b6d3add

62b86b057..566ce1b1e 389-ds-base-1.3.8 -> 389-ds-base-1.3.8

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.3.8 (was: 1.3.7.0)

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

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

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 (was: fixed)
Metadata
None
None
None
None
review
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.