Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1199060 - Replication agreement with replica not disabled when ipa-restore done without IPA installed
Replication agreement with replica not disabled when ipa-restore done without...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.1
Unspecified Unspecified
medium Severity high
: rc
: ---
Assigned To: IPA Maintainers
Namita Soman
: ZStream
Depends On: 1187524
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-05 07:26 EST by Jan Kurik
Modified: 2015-03-26 11:50 EDT (History)
11 users (show)

See Also:
Fixed In Version: ipa-4.1.0-18.el7_1.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1187524
Environment:
Last Closed: 2015-03-26 11:50:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0728 normal SHIPPED_LIVE Moderate: ipa and slapi-nis security and bug fix update 2015-03-26 15:50:25 EDT

  None (edit)
Description Jan Kurik 2015-03-05 07:26:03 EST
This bug has been copied from bug #1187524 and has been proposed
to be backported to 7.1 z-stream (EUS).
Comment 6 Namita Soman 2015-03-16 11:31:24 EDT
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
Comment 7 Namita Soman 2015-03-16 13:43:17 EDT
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
Comment 9 errata-xmlrpc 2015-03-26 11:50:43 EDT
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

Note You need to log in before you can comment on or make changes to this bug.