#49540 Indexing task is reported finished too early regarding the backend status
Closed: fixed 3 months ago by mreynolds. Opened 2 years ago by tbordaz.

Issue Description

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

Package Version and Platform

All version

Steps to reproduce

  1. Too dynamic for a systematic TC

Actual results

Receives a err=53 after task complete

Expected results

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

2 years ago

Metadata Update from @tbordaz:
- Issue set to the milestone: 1.3.7 backlog

2 years ago
2 years ago

Metadata Update from @lkrispen:
- Custom field reviewstatus adjusted to ack (was: None)

2 years ago

Merge previous patch with the testcase

0002-Ticket-49540-Indexing-task-is-reported-finished-too-.patch

Metadata Update from @tbordaz:
- Custom field reviewstatus adjusted to review (was: ack)

2 years ago

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)

2 years ago

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)

3 months ago

Login to comment on this ticket.

Metadata