Bug 1924848

Summary:	Negative wtime on ldapcompare
Product:	Red Hat Enterprise Linux 8	Reporter:	Viktor Ashirov <vashirov>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	aadhikar, ldap-maint, mreynolds, sgouvern
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:	389-ds-1.4-8050020210514191740-d5c171fc	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 18:11:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Viktor Ashirov 2021-02-03 18:11:08 UTC

Description of problem:
Compare operation generates negative wtime in the access log.

Version-Release number of selected component (if applicable):
389-ds-base-1.4.3.8-6.module+el8.3.0+8995+c08169ba.x86_64

How reproducible:
always

Steps to Reproduce:
1. ldapcompare -D uid=user,dc=example,dc=com -w password cn=demo_group,ou=groups,dc=example,dc=com gidNumber:9999


Actual results:
[03/Feb/2021:18:07:58.251465934 +0000] conn=12 op=0 BIND dn="uid=user,dc=example,dc=com" method=128 version=3
[03/Feb/2021:18:07:58.252098372 +0000] conn=12 op=0 RESULT err=0 tag=97 nentries=0 wtime=0.000182726 optime=0.000675624 etime=0.000854818 dn="uid=user,dc=example,dc=com"
[03/Feb/2021:18:07:58.252518220 +0000] conn=12 op=1 CMP dn="cn=demo_group,ou=groups,dc=example,dc=com" attr="gidNumber"
[03/Feb/2021:18:07:58.252746534 +0000] conn=12 op=1 RESULT err=5 tag=111 nentries=0 wtime=-161634.769201119 optime=161633.231282362 etime=0.000478713
[03/Feb/2021:18:07:58.502988956 +0000] conn=12 op=2 UNBIND
[03/Feb/2021:18:07:58.503016718 +0000] conn=12 op=2 fd=65 closed error - U1



Expected results:
wtime should be positive.

Additional info:

Comment 1 mreynolds 2021-02-03 18:56:13 UTC

Both wtime & optime are wrong.  I think this feature simply missed "compare" operations, should be a simple fix...

Comment 2 mreynolds 2021-03-29 19:23:26 UTC

Upstream ticket:

https://github.com/389ds/389-ds-base/issues/4706

Comment 7 Akshay Adhikari 2021-05-31 10:04:52 UTC

Build Tested: 389-ds-base-1.4.3.23-1.module+el8.5.0+11016+7e7e9011.x86_64

============================================================================ test session starts =================================================================
platform linux -- Python 3.6.8, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3.6
cachedir: .pytest_cache
metadata: {'Python': '3.6.8', 'Platform': 'Linux-4.18.0-305.8.el8.x86_64-x86_64-with-redhat-8.5-Ootpa', 'Packages': {'pytest': '6.2.4', 'py': '1.10.0', 'pluggy': '0.13.1'}, 'Plugins': {'metadata': '1.11.0', 'html': '3.1.1', 'ignore-flaky': '2.0.0'}}
389-ds-base: 1.4.3.23-1.module+el8.5.0+11016+7e7e9011
nss: 3.53.1-17.el8_3
nspr: 4.25.0-2.el8_2
openldap: 2.4.46-16.el8
cyrus-sasl: not installed
FIPS: disabled
rootdir: /workspace/ds/dirsrvtests, configfile: pytest.ini
plugins: metadata-1.11.0, html-3.1.1, ignore-flaky-2.0.0
collected 1 item                                                                                                                                                            

dirsrvtests/tests/suites/ds_logs/ds_logs_test.py::test_optime_and_wtime_keywords PASSED                                                                               [100%]

====================================================================== 1 passed, 25 warnings in 15.21s ===========================================================

-> Marking as verified: tested.

Comment 8 sgouvern 2021-05-31 10:09:48 UTC

As per comment 7, marking as VERIFIED

Comment 11 errata-xmlrpc 2021-11-09 18:11:20 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (389-ds-base bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4203