This bug is created as a clone of upstream ticket:
Description of problem:
There appears to be a race failing when the DNA Plugin attempts to make a uid
range replication request backed by gssapi.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install IPA Server (ipa-server-install)
2. Prepare Replica (ipa-replica-prepare replica-hostname)
3. Transfer resulting replica-hostname.gpg
4. Install Replica (ipa-replica-install replica-hostname.gpg)
5. kinit admin
6. Attempt to create new user (ipa user-add test)
ipa: ERROR: Operations error: Allocation of a new value for range cn=posix
ids,cn=distributed numeric assignment plugin,cn=plugins,cn=config failed!
Unable to proceed.
Expected new user to be added and range to be transferred.
Please add steps to reproduce/verify with just RHDS
(In reply to comment #1)
> Please add steps to reproduce/verify with just RHDS
Do a 2 master replication WAN test with both servers set up to do DNA and range requests - might be able to use the existing DNA test suite, just using WAN replication
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: Using replication with DNA to auto-generate UID numbers.
Consequence: Adding users fails with error messages like this:
Operations error: Allocation of a new value for range cn=posix
ids,cn=distributed numeric assignment plugin,cn=plugins,cn=config failed
Fix: DNA was using a too-short timeout value that was causing problems on networks with high latency (WANs, etc.). The fix was to use the correct timeout value specified in the replication configuration.
Result: No errors adding users when using replication with DNA.
Tested DNA plugin with ranges o LAN. I didn't see any error messages. Hence marking the bug as verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.