#51241 New access log time keywords have bogus values for extended ops
Closed: wontfix by spichugi. Opened by mreynolds.

Issue Description

[13/Aug/2020:11:22:41.178044221 -0400] conn=64 op=29 EXT oid="2.16.840.1.113730.3.5.5" name="replication-multimaster-extop"
[13/Aug/2020:11:22:41.179185259 -0400] conn=64 op=29 RESULT err=0 tag=120 nentries=0 wtime=-530917.627728353 optime=530916.373526270 etime=0.001250892

With extended ops one of the counters is wrong (uninitialized?)

Package Version and Platform

Steps to reproduce

1.
2.
3.

Actual results

Expected results


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.3

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

Fix for extended ops:

Commit dda3ab0d fixes this issue

357d28bd2..25eaefe06 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

674dc76bf..1b05d81a2 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

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

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
- Issue status updated to: Closed (was: Open)

Metadata