Details
-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
None
-
None
Description
AD creates conflict objects when hitting two servers at same time.
2019-08-09 22:51:08,247: [FullSyncer(pspng_oneprodFull)-Thread] ERROR LdapGroupProvisioner.fetchTargetSystemGroups(546) - pspng_oneprodFull-full: Search for group penn:community:employee:org:06XX:06XX_rolluporg_includes/#177179(Existing) with '[org.ldaptive.SearchFilter@-291495045::filter=(&(objectclass=group)(gidNumber=177179)), parameters={}]' returned multiple matches: [LdapObject[id=365784,cn=06XX_rolluporg_includes |
CNF:7a4e4cf4-b2dd-445c-bec6-9d4d11b1a3cd,samAccountName=$4E2500-2OSD2K1HT2UH,dn=cn=06xx_rolluporg_includes\0acnf:7a4e4cf4-b2dd-445c-bec6-9d4d11b1a3cd,ou=06xx,ou=org,ou=employee,ou=community,ou=penn,ou=grouperfull,ou=365groups,dc=one,dc=upenn,dc=edu,provisioner=LdapGroupProvisioner[pspng_oneprodFull-full]], LdapObject[id=365785,cn=06XX_rolluporg_includes,samAccountName=$3D3500-73VMHQ0MNOQA,dn=cn=06xx_rolluporg_includes,ou=06xx,ou=org,ou=employee,ou=community,ou=penn,ou=grouperfull,ou=365groups,dc=one,dc=upenn,dc=edu,provisioner=LdapGroupProvisioner[pspng_oneprodFull-full]]] |
|
PSPNG could automatically delete the CNF conflict objects (and schedule a full sync for the group) and log an error suggesting to point to a domain name with more sensible load balancing (active/standby instead of round robin active/active)