Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1676948
Description of problem: After audit log file is rotated, DS version string is logged after each update. For example: time: 20190213161354 dn: uid=test_audit_log,ou=People,dc=example,dc=com result: 0 changetype: modify replace: description description: test - replace: modifiersname modifiersname: cn=directory manager - replace: modifytimestamp modifytimestamp: 20190213161354Z - 389-Directory/1.4.0.21 B2019.031.1515 server-f28.example.com:38901 (/etc/dirsrv/slapd-standalone1) time: 20190213161354 dn: uid=test_audit_log,ou=People,dc=example,dc=com result: 0 changetype: modify replace: description description: test - replace: modifiersname modifiersname: cn=directory manager - replace: modifytimestamp modifytimestamp: 20190213161354Z - 389-Directory/1.4.0.21 B2019.031.1515 server-f28.example.com:38901 (/etc/dirsrv/slapd-standalone1) time: 20190213161355 dn: cn=uniqueid generator,cn=config result: 0 changetype: modify replace: nsState nsState:: gA6DUaov6QHW0IapRgvYvQEAAAAAAAAA - replace: modifiersname modifiersname: cn=server,cn=plugins,cn=config - replace: modifytimestamp modifytimestamp: 20190213161355Z Version-Release number of selected component (if applicable): 389-ds-base-1.4.0.20-7.module+el8+2750+1f4079fb.x86_64 How reproducible: always Steps to Reproduce: 1. Enable audit log 2. Set nsslapd-auditlog-maxlogsize to 1 3. Do lots of mods, so that audit file is rotated 4. Check audit log file. Actual results: Audit log file contains DS version string. Expected results: No DS version string in the audit log. Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1676948
Metadata Update from @mreynolds: - Issue assigned to mreynolds
https://pagure.io/389-ds-base/pull-request/50537
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE)
Commit 71d7ca0 relates to this ticket
c1e1b80..0f5d020 389-ds-base-1.4.0 -> 389-ds-base-1.4.0
66969b2..51f3026 389-ds-base-1.3.10 -> 389-ds-base-1.3.10
060aa81..5eabd88 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
071b13e..f4133b7 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit fb3d355 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/3592
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)
Log in to comment on this ticket.