Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Cloned from upstream: https://pagure.io/freeipa/issue/7605


### Issue
During parallel ipa-replica-install, each replica will connect to the master and send their updates.
There is a good chance that a replica agreement (replica->master) will find the master being BUSY (acquired by an other replica).

This is normal and replica will backoff for sometime. It can lead to ipa-replica-install timeout.

It could be helpfull to reduce nsds5ReplicaReleaseTimeout=10 during that intensive period of parallel install


#### Steps to Reproduce
1. Similar test case of https://pagure.io/freeipa/issue/7595 with 4 replicas parallel install


#### Actual behavior
ipa-replica-install times out

#### Expected behavior
Should not

Upstream ticket:
https://pagure.io/freeipa/issue/7605

Fixed upstream:

master: 811b0fdb4620938963f1a29d3fdd22257327562c

This is in the release-4-7-0 release tag.

https://pagure.io/freeipa/issue/7605 was addressed with the fix for https://pagure.io/freeipa/issue/7617. The fix for 7617 was included in 7.6 (BZ 1623112 fixed in ipa-4.6.4-7.el7).

Hence we can close this BZ.

Fixed upstream
master:
    811b0fd Tune DS replication settings
    02f4a7a DS replication settings: fix regression with <3.3 master

ipa-4-6:
    6ba653c Tune DS replication settings
    2563f6f DS replication settings: fix regression with <3.3 master

ipa-4-5:
    ec60901 replicainstall: DS SSL replica install pick right certmonger host
    5ef8333 Fix race condition in get_locations_records()
    a9cc862 Tune DS replication settings
    79fe981 Auto-retry failed certmonger requests
    f3dd0cb Wait for client certificates
    f4ee36a DS replication settings: fix regression with <3.3 master

ipa-4-7:
    30443d1 DS replication settings: fix regression with <3.3 master