The current replication agmt default timeout is 10 minutes, and this is very high for typical deployments. It should be lowered by default to meet the most common use cases, and only raised if needed.
Suggested to move it to 120 seconds instead of 600.
Metadata Update from @mreynolds: - 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=1419050
https://pagure.io/389-ds-base/pull-request/50274
commit a703d1017716159f9c84b2c8f6fb0246f9a6a8a8 master branch
0654777e7..951c499d9 389-ds-base-1.4.0 -> 389-ds-base-1.4.0
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/3332
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)