At the moment, if entries are skiped due to the fifo.bsize being exceeded our tools still return an exit status of 0.
With the new dynamic allocation it should be rare, if ever that an import / index task fails due to buffer size allocations.
In the case it does happen, a skipped entry is a bad situation. A skipped entry during indexing, means the entry can't be searched for. A skipped entry in an import means the entry no longer exists.
As a result, our tasks in the case of an entry being skipped, should set a non-0 return code.
Per triage, push the target milestone to 1.3.6.
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.6.0
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: 1.3.7 backlog (was: 1.3.6.0)
Metadata Update from @mreynolds: - Issue assigned to mreynolds (was: nhosoi)
I think we can close this as I eliminated the fault. the fife buffer dynamically expands during the operation rather than returning an error.
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: worksforme - 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/1804
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: worksforme)
Login to comment on this ticket.