At the beginning of an import, a flag is set to mark the target backend is busy. This flag is set before checking if there are pending operations. If such operations exist the import can not proceed and fails. The problem is that in such case of pending operations, the import fails without resetting the busy flag. It let the backend busy (until next reboot) and prevent new import.
All version
The backend stay busy without possibility to repair it (import)
A transient failure is normal but should leave the backend ready for import
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1642838 - Custom field type adjusted to None - Custom field version adjusted to None
https://pagure.io/389-ds-base/pull-request/50119
a3d35b9dd..ff00b0740 master
Fix compiler warning
eae696f1e..58be90b8b master -> master
Cherry-picked to 1.3.9
c9580477 Ticket 49540 - FIx compiler warning in ldif2ldbm 630940ec1 Ticket 50117 - after certain failed import operation, impossible to replay an import operation
de73f4f6d (HEAD -> 389-ds-base-1.3.8, origin/389-ds-base-1.3.8) Ticket 49540 - FIx compiler warning in ldif2ldbm a56280287 Ticket 50117 - after certain failed import operation, impossible to replay an import operation
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit 0362fa3f relates to this ticket
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/3176
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)