There is a limit on the number of cleanAllRUV tasks that can be running at once. But this limit is not checked for incoming replicated tasks. It is only checked when the original task is created. This can allow for thousands of clean tasks/threads to be created.
The limit needs to be checked when cleanallruv extended operations are received.
https://pagure.io/389-ds-base/pull-request/50539
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Commit 3575730 relates to this ticket
0f5d020..ab24aa4 389-ds-base-1.4.0 -> 389-ds-base-1.4.0
51f3026..a6f9e10 389-ds-base-1.3.10 -> 389-ds-base-1.3.10
5eabd88..5956610 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1739182
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit 21ba842 relates to this ticket
This just moved the CI test to a standalone file
2855482..78567d7 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
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/3594
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.