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.
Cloned from upstream: https://pagure.io/freeipa/issue/7228
On Fedora 27, build from master, git up-date-today.
I did a very typical installation of a single master plus one replica with no additional services:
Install on master: ipa-server-install -a password -p password -r EXAMPLE.COM -U
Install on replica1: ipa-replica-install --server master.example.com --domain example.com
I wanted to see how initialize left and right worked so I took a look at the topology:
```
# ipa topologysegment-find domain
------------------
0 segments matched
------------------
----------------------------
Number of entries returned 0
----------------------------
```
Oh, odd. Where is the agreement:
```
repica1 # ipa-replica-manage list -v replica1.example.com
master.example.com: replica
last init status: None
last init ended: 1970-01-01 00:00:00+00:00
last update status: Error (0) Replica acquired successfully: Incremental update succeeded
last update ended: 2017-10-30 17:00:04+00:00
```
UI confirms that there are two nodes and no connections.
How is this possible?
Domainlevel is 1
Even worse I used the UI to create a connection between master and replica1 and now I have TWO agreements:
```
replica1 # ipa-replica-manage list -v replica1-example.com
master.example.com: replica
last init status: None
last init ended: 1970-01-01 00:00:00+00:00
last update status: Error (0) Replica acquired successfully: Incremental update succeeded
last update ended: 2017-10-30 17:29:51+00:00
master.example.com: replica
last init status: None
last init ended: 1970-01-01 00:00:00+00:00
last update status: Error (0) Replica acquired successfully: Incremental update succeeded
last update ended: 2017-10-30 17:29:49+00:00
So now this is very, very bad.
# ipa topologysuffix-verify domain
====================================================
Replication topology of suffix "domain" is in order.
====================================================
```
Yeah, not so much.