This is a transient issue. In ldbm_back_ldbm2index, the task completion status is reported finished but the backend remains busy while some cleanup are done. Because of dynamic (contention on inst->inst_config_mutex, entry/idl/cursor to free), a client monitoring the task status may send update to the backend too early regarding its status
All version
Receives a err=53 after task complete
Should accept update after task comlete
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to IPA - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1535302 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @tbordaz: - Issue set to the milestone: 1.3.7 backlog
Metadata Update from @tbordaz: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1536141 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1535302)
<img alt="0001-Ticket-49540-Indexing-task-is-reported-finished-too-.patch" src="/389-ds-base/issue/raw/files/ae8a15cb51d77c34a0c5f92dddb75ac0012c7627697624d1d4a42c76792b40fd-0001-Ticket-49540-Indexing-task-is-reported-finished-too-.patch" />
Metadata Update from @lkrispen: - Custom field reviewstatus adjusted to ack (was: None)
Merge previous patch with the testcase
<img alt="0002-Ticket-49540-Indexing-task-is-reported-finished-too-.patch" src="/389-ds-base/issue/raw/files/0ab5b7715033b642e82f2fa08ef431f6a22aa5cfa8375f64db1fc5f6997b531a-0002-Ticket-49540-Indexing-task-is-reported-finished-too-.patch" />
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to review (was: ack)
test case looks also good, just the comment in :expectedresults: is not adapted to the test case.
Metadata Update from @lkrispen: - Custom field reviewstatus adjusted to ack (was: review)
Thanks lkrispen for the review and remark. I updated the testcase
To ssh://pagure.io/389-ds-base.git b3768e6..cb7bda3 master -> master
To ssh://pagure.io/389-ds-base.git b4fbcf0..873d48c 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2599
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)
Login to comment on this ticket.