389-ds-base

#49202 Referential integrity has it's own log file: it shouldn't
Closed: wontfix Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

Remove the referential integrity log file and use the correct slapi-log types.

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new
- Custom field type adjusted to defect
- Issue tagged with: Easyfix

Metadata Update from @mreynolds:
- Custom field reviewstatus reset (from new)
- Issue set to the milestone: 1.4 backlog

Metadata Update from @ilias95:
- Issue assigned to ilias95

This log file is used for other purposes than real logging. It is actually used for implementing referint's async mode.

There is an active discussion about whether a queue should be used instead, or even getting rid of the async mode completely, but it doesn't directly apply here: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org/thread/DB5YKUV4A2LVPPXP72OJ4KQC2H2B4G3W/?sort=date

Metadata Update from @ilias95:
- Issue close_status updated to: invalid
- 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/2261

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: invalid)
Metadata

Easyfix

None
None
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.