RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1663829 - import task should not be deleted after import finishes to be able to query the status.
Summary: import task should not be deleted after import finishes to be able to query t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 7.7
Assignee: thierry bordaz
QA Contact: RHDS QE
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks: 1672173
TreeView+ depends on / blocked
 
Reported: 2019-01-07 08:18 UTC by German Parente
Modified: 2020-09-13 22:18 UTC (History)
11 users (show)

Fixed In Version: 389-ds-base-1.3.9.1-1.el7
Doc Type: Bug Fix
Doc Text:
.The time after which Directory Server deletes tasks has been changed Previously, Directory Server deleted task entries 2 minutes after a task finished. As a consequence, applications that were monitoring the task could miss the task result. This update changes the time after which the server deletes tasks. By default, all completed tasks are now deleted after 1 hour, except import and export tasks, which are deleted 24 hours after completion.
Clone Of:
: 1672173 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:59:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3236 0 None closed import task should not be deleted too rapidely after import finishes to be able to query the status. 2021-02-01 13:18:34 UTC
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:59:32 UTC

Description German Parente 2019-01-07 08:18:34 UTC 
Description of problem:

when we do an on-line import, independently of the result of the task (failure or success), the task should not be deleted as it's the case today but kept for a while so as to be able to query the status.


Version-Release number of selected component (if applicable): latest rhel-7.6 version


How reproducible: always
Comment 2 thierry bordaz 2019-01-07 09:21:36 UTC 
Regarding failing tasks, it calls destroy_task (immediate DEL of the task). It should be possible to call slapi_task_finish (deferred DEL).
Regarding successful task, import code is much different from others tasks code. At first look successful import should eventually calls slapi_task_finish but it does not take this path.
Comment 5 thierry bordaz 2019-01-21 16:27:12 UTC 
The problem is a task configuration issue.

When the task completes it registers a time event to delete the task entry. By default the task entry is kept for 2minutes then removed. The maximum duration of a completed task is 1hour.
It can be tuned with the 'ttl' attribute of the created task.
The default is likely too low (2min), will evaluate the appropriate value.

Unfortunately the ldif2db.pl script does not provide the ability to configure it.

Could you try the workaround (For example, setting timeout to 15min)

195,196c195
< $ttl = "ttl: 900";
< $entry = "${dn}${misc}${cn}${nsinstance}${nsincluded}${nsexcluded}${nsldiffiles}${nsnoattrindexes}${nsimportencrypt}${nsmergechunksiz}${nsgenuniqid}${nsuniqidname}${ttl}";
---
> $entry = "${dn}${misc}${cn}${nsinstance}${nsincluded}${nsexcluded}${nsldiffiles}${nsnoattrindexes}${nsimportencrypt}${nsmergechunksiz}${nsgenuniqid}${nsuniqidname}";
Comment 6 thierry bordaz 2019-01-22 12:10:38 UTC 
Upstream ticket:
https://pagure.io/389-ds-base/issue/50177
Comment 7 thierry bordaz 2019-02-01 15:31:41 UTC 
Fix pushed upstream -> POST
Comment 10 bsmejkal 2019-04-23 07:49:53 UTC 
Build tested:
389-ds-base-1.3.9.1-4.el7.x86_64

# export_2019_4_23_3_23_11, export, tasks, config
dn: cn=export_2019_4_23_3_23_11,cn=export,cn=tasks,cn=config
objectClass: top
objectClass: extensibleObject
cn: export_2019_4_23_3_23_11
nsinstance: userRoot
nsincludesuffix: dc=example,dc=com
nsexportreplica: true
nsuseonefile: true
nsfilename: /tmp/export.ldif
ttl: 86400
nstaskcurrentitem: 1
nstasktotalitems: 1
nstasklog:: QmVnaW5uaW5nIGV4cG9ydCBvZiAndXNlclJvb3QnCnVzZXJSb290OiBQcm9jZXNzZW
 QgOSBlbnRyaWVzICgxMDAlKS4KRXhwb3J0IGZpbmlzaGVkLg==
nstaskstatus: userRoot: Processed 9 entries (100%).
nstaskexitcode: 0

db2ldif task is now created with ttl: 84000 instead of 120. Same value is present for import task.

Marking as Verified.
Comment 14 errata-xmlrpc 2019-08-06 12:59:10 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, 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-2019:2152
Note You need to log in before you can comment on or make changes to this bug.