The content sync plugin does not correctly maintain the thread count when connections get aborted. This causes the server shutdown to hang.
This is a regression caused by https://pagure.io/389-ds-base/issue/48048
https://pagure.io/389-ds-base/c/94d4b10ea12e063e78c03ef64ba5c8cfb71286e1
389-ds-base-1.3.3 are affected
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to new - Custom field type adjusted to defect - Issue priority set to: 3 - Issue set to the milestone: 1.3.4.11
Metadata Update from @mreynolds: - Issue assigned to mreynolds
<img alt="0001-Issue-49170-sync-plugin-thread-count-not-handled-cor.patch" src="/389-ds-base/issue/raw/files/fa65567591599905f6ddf3448efbcfb88386e86562b9169fd4783437417ee7c5-0001-Issue-49170-sync-plugin-thread-count-not-handled-cor.patch" />
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: new) - Custom field version adjusted to 1.3.4
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to new (was: review) - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1432206 - Custom field version reset
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: new)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: ack)
Metadata Update from @nhosoi: - Custom field reviewstatus adjusted to ack (was: review)
b1b0574..770fcf4 master -> master
d8338ef..d0d8e6e 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
8a758af..ceb7331 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
96c8765..0cf20b4 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - 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/2229
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.