389-ds-base

#50119 Ticket 50117 - after certain failed import operation, impossible to replay an import operation
Closed by spichugi. Opened by tbordaz.
tbordaz/389-ds-base ticket_50117  into  master

Download 50119.patch

Bug Description:
At the beginning of an import, a flag is set to mark the target backend is busy.
Then import tests 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.

Fix Description:
It needs to reset the busy flag if there are pending operations

https://pagure.io/389-ds-base/issue/50117

Reviewed by: ?

Platforms tested: F27

Flag Day: no

Doc impact: no

More of a grammar issue here. This should read something like: "ldbm: '%s' there are %d pending operation(s)." The rest looks good ACK!

Ack from me too :)

rebased onto 784c16e0a478ed26c3d57e75cc7ffd2c8b21ddb6

rebased onto ff00b07402747aac403478a157adab75e306d7d1

Pull-Request has been merged by tbordaz

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3178

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.