Red Hat Bugzilla – Bug 1199060
Replication agreement with replica not disabled when ipa-restore done without IPA installed
Last modified: 2015-03-26 11:50:43 EDT
This bug has been copied from bug #1187524 and has been proposed to be backported to 7.1 z-stream (EUS).
Verified using ipa-server-4.1.0-18.el7_1.1.x86_64 Steps taken: 1> Installed master, replica 2> on master, added user - one 3> on replica, added user - two 4> on master - ipa user-find - lists admin, one, two 5> on replica - ipa user-find - lists admin, one, two 6> on master - took backup with users one, and two 7> on master - deleted user one, added user three 8> on replica - deleted user two, added user four 9> on master - ipa user-find - lists admin, three, four 10> on replica - ipa user-find - lists admin, three, four 11> on master - uninstall server 12> on master - restore using backup created above 13> on master - VERIFIED ipa user-find - lists admin, one, two 14> on replica - ipa user-find - lists admin, three, four
Also followed up with steps below - to verify expected behaviour when replication is restarted: # ipa-replica-manage list hp-dl385gen8-01.testrelm.test: master dell-per320-01.testrelm.test: master # ipa-replica-manage connect hp-dl385gen8-01.testrelm.test A replication agreement to hp-dl385gen8-01.testrelm.test already exists To restore everything to the state of the master, on replica ran: # ipa-replica-manage re-initialize --from <master hostname> ipa: INFO: Setting agreement cn=meTohp-dl385gen8-01.testrelm.test,cn=replica,cn=dc\=testrelm\,dc\=test,cn=mapping tree,cn=config schedule to 2358-2359 0 to force synch ipa: INFO: Deleting schedule 2358-2359 0 from agreement cn=meTohp-dl385gen8-01.testrelm.test,cn=replica,cn=dc\=testrelm\,dc\=test,cn=mapping tree,cn=config Update in progress, 3 seconds elapsed Update succeeded on master, replica - ipa user-find - lists admin, one, two on master - added user five on master, replica - ipa user-find - lists admin, one, two, five
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. https://rhn.redhat.com/errata/RHSA-2015-0728.html