Dmitry Perets via FreeIPA-users wrote:
You might want to look for replication conflicts. Maybe one entry is
hung up.
rob
Hi Rob, you mean on the WORKING IPA?
Because indeed, now it looks more weird that one is WORKING rather than that the other is
NOT WORKING...
I've tested on yet another one, this time running CentOS (!), also freeipa 4.6.4.
And I see the same problem:
[13/Jun/2019:18:42:12.013877786 +0200] conn=189796 op=2 SRCH base="cn=staged
users,cn=accounts,cn=provisioning,dc=dths37,dc=dcn,dc=telekom,dc=de" scope=1
filter="(objectClass=posixaccount)" attrs="telephoneNumber sshpubkeyfp
ipaSshPubKey uid krbCanonicalName title loginShell uidNumber gidNumber sn homeDirectory
mail krbPrincipalName givenName nsAccountLock"
[13/Jun/2019:18:42:12.015946649 +0200] conn=189796 op=2 RESULT err=0 tag=101 nentries=0
etime=0.0002280480
So definitely it looks like a bug with IPA 4.6.4.
And why one of my IPAs nevertheless works - don't know, but maybe we can ignore it for
now...