+++ This bug was initially created as a clone of Bug #2123682 +++ Description of problem: When creating a memberof fixup task, the startup time ('Started') is invalid and also result on an invalid 'Elapsed time' dsconf localhost plugin memberof fixup -f "(objectclass=inetOrgPerson)" "dc=example,dc=com" Adding fixup task entry... Successfully added task entry "cn=memberOf_fixup_2022-09-02T11:44:24.283059,cn=memberOf task,cn=tasks,cn=config". This task is running in the background. To track its progress you can use the "fixup-status" command. dsconf localhost plugin memberof fixup-status Found 1 fix-up task [1] Task: cn=memberOf_fixup_2022-09-02T11:44:24.283059,cn=memberOf task,cn=tasks,cn=config -------------------------------------------------------------------------------- - Base DN: dc=example,dc=com - Filter: (objectclass=inetorgperson) - Status: - Started: Fri Sep 2 10:44:24 2022 (20220902094424Z) - Ended: - Elapsed Time: 1:13:31 - Exit Code: Not finished ... Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Install instances with memberof enabled 2. provision groups/members 3. dsconf localhost plugin memberof fixup -f "(objectclass=inetOrgPerson)" "dc=example,dc=com" 4. dsconf localhost plugin memberof fixup-status Actual results: Invalid 'Started' and 'Elapsed Time' Expected results: Should be correct time --- Additional comment from on 2022-11-16 16:15:01 UTC --- Upstream ticket: https://github.com/389ds/389-ds-base/issues/5413
Automated test passes: ============================================ test session starts ============================================= platform linux -- Python 3.9.16, pytest-6.2.2, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3 cachedir: .pytest_cache 389-ds-base: 2.2.6-1.module+el9dsrv+17949+63c5b04e nss: 3.79.0-14.el9_0 nspr: 4.34.0-14.el9_0 openldap: 2.6.2-3.el9 cyrus-sasl: not installed FIPS: disabled rootdir: /mnt/tests/rhds/install/ds/dirsrvtests, configfile: pytest.ini collected 1 item dirsrvtests/tests/suites/memberof_plugin/fixup_test.py::test_fixup_task_limit PASSED [100%] ============================================= 1 passed in 48.74s ============================================ Checking the output manually: On the previous version: [2] Task: cn=memberOf_fixup_2023-02-21T05:48:20.216910,cn=memberOf task,cn=tasks,cn=config -------------------------------------------------------------------------------- - Base DN: dc=example,dc=com - Filter: (objectclass=*) - Status: Processed 5000 entries in 0 seconds (+0 seconds) - Started: Tue Feb 21 10:48:20 2023 (20230221104820Z) - Ended: - Elapsed Time: -1 day, 19:00:02 - Exit Code: Not finished ... On the current (fixed) version: [3] Task: cn=memberOf_fixup_2023-02-21T05:49:59.916905,cn=memberOf task,cn=tasks,cn=config -------------------------------------------------------------------------------- - Base DN: dc=example,dc=com - Filter: (objectclass=*) - Status: Processed 5000 entries in 1 seconds (+0 seconds) - Started: Tue Feb 21 10:49:59 2023 (20230221104959Z) - Ended: - Elapsed Time: - Exit Code: Not finished ... Marking as VERIFIED.
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 (redhat-ds:12 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-2023:3344