If we attempt to reinitialize a replication agreement and a replication agreement for the local server cannot be found on the remote server we raise an unhandled NotFound exception:
# ipa-replica-manage re-initialize --from=pacer.example.com Directory Manager password: Traceback (most recent call last): File "/usr/sbin/ipa-replica-manage", line 896, in <module> main() File "/usr/sbin/ipa-replica-manage", line 866, in main re_initialize(realm, host, options.fromhost, dirman_passwd) File "/usr/sbin/ipa-replica-manage", line 783, in re_initialize repl.force_sync(repl.conn, thishost) File "/usr/lib/python2.7/site-packages/ipaserver/install/replication.py", line 988, in force_sync DN(('cn', 'config')), ldap.SCOPE_SUBTREE, filter) File "/usr/lib/python2.7/site-packages/ipaserver/ipaldap.py", line 453, in getList raise errors.NotFound(reason=arg_desc) ipalib.errors.NotFound: base="cn=config", scope=2, filterstr="(&(|(&(objectclass=nsds5ReplicationAgreement)(nsDS5ReplicaRoot=dc=example,dc=com))(objectclass=nsDSWindowsReplicationAgreement))(nsDS5ReplicaHost=valient.example.com))"
I generated this during backup and restore testing. It can also be reproduced by using ldapmodify to delete the agreement before attemping a reinitialize.
We should catch this and say something like "no agreement found on server X"
Was already fixed. Probably as a side effect of other fix.
ipa-replica-manage -p Secret123 re-initialize --from=a.example.com 'b.example.com' has no replication agreement for 'a.example.com'
Metadata Update from @rcritten: - Issue assigned to simo - Issue set to the milestone: FreeIPA 4.2
Login to comment on this ticket.