I'm running 389ds 2.0.15 on a two node cluster in a multi master mode. I'm using the DNA plugin to generate unique uid numbers for new accounts. Each directory instance is assigned a unique range of uid numbers. It works in so far as it assigns a uid number when it gets the magic token but whatever is supposed to be verifying that the uid number is not already assigned is not working.
Do you mean on the same instance a uidNumber are being duplicated, or that the other supplier is assigning a uidNumebr that is already present on the other supplier replica?
Can you please provide the DNA config from both replicas, and the shared config entries?
I've cranked the error log level up, but I don't get anything in the logs that is helpful in determining why that validation is not working correctly.
# ansible-managed-uidnumber-generation, Distributed Numeric Assignment Plugin,plugins, configdn: cn=ansible-managed-uidnumber-generation,cn=Distributed Numeric AssignmentPlugin,cn=plugins,cn=configobjectClass: topobjectClass: dnaPluginConfigcn: ansible-managed-uidnumber-generationdnaType: uidNumberdnaNextValue: 62009dnaMaxValue: 131000dnaMagicRegen: generatednaFilter: (objectclass=posixAccount)dnaScope: ou=Accounts,dc=example,dc=edudnaSharedCfgDN: ou=ranges,ou=Accounts,dc=example,dc=edu
I'm stumped. Anyone have any direction on how to debug this further?
_______________________________________________ 389-users mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://email@example.com Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- Directory Server Development Team