Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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