Cleanallruv is not logging anythign in 1.3.6
There are two issues here.
[1] During the error log refactoring a mistake was made that prevented most of the logging from taking place:
https://pagure.io/389-ds-base/issue/48978
[2] We also changed the logging to work in only debug builds (not sure why). Perhaps to keep error log from, bloating?
Metadata Update from @mreynolds: - Issue assigned to mreynolds
<img alt="0001-Ticket-49439-cleanallruv-is-not-logging-information.patch" src="/389-ds-base/issue/raw/files/f8ce257c8c7e5f03b6b4dafb127ec86eba88dc9d9d387e35866c9144182abc1e-0001-Ticket-49439-cleanallruv-is-not-logging-information.patch" />
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
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1509016
Happy with this. Is there a reason we use cleanruv log instead of a direct call to log_error? Maybe a future cleanup?
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
Because we need to pass the vargs, I'm not sure we can use slapi_log_err() for that.
f6b0e18..e1f866a master -> master
1b04a2d..b94a648 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
7cbeed8..9141829 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
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/2498
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.