Description of problem: cl-dump utility generates .ldif files in the changelog directory. At the end, they are renamed to ldif.done but they are never deleted.
And in some cases, these files can be very large which is provoking an issue at a customer.
Version-Release number of selected component (if applicable):
How reproducible: very simple by running cl-dump.pl
Cloned from BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1685059
https://pagure.io/389-ds-base/pull-request/50573
Metadata Update from @spichugi: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Also cherry-picked to: 40c9a5a..0db15f5 389-ds-base-1.3.9 -> 389-ds-base-1.3.9 52df7d9..5c039fa 389-ds-base-1.3.10 -> 389-ds-base-1.3.10
Metadata Update from @spichugi: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1685059
Metadata Update from @spichugi: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit 51e2c45 relates to this ticket
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/3628
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.