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.
Bug 1704796 - Wrong CA replication topology created with two replicas
Summary: Wrong CA replication topology created with two replicas
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-30 14:23 UTC by Sergey Orlov
Modified: 2019-08-06 13:09 UTC (History)
6 users (show)

Fixed In Version: ipa-4.6.5-8.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:09:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2241 0 None None None 2019-08-06 13:09:54 UTC

Description Sergey Orlov 2019-04-30 14:23:06 UTC 
Description of problem:
When installing ipa server with two replicas in a "star" topology I get star topology for "domain" suffix and line topology for "ca" suffix.

Version-Release number of selected component (if applicable):
ipa-server-4.6.5-6.el7.x86_64

How reproducible:
4 of 6 times in my experiments


Steps to Reproduce:

Having 3 machines with hostnames master1.testrelm.test, replica1.testrelm.test, replica2.testrelm.test
1. On master1 execute:
ipa-server-install -n testrelm.test -r TESTRELM.TEST -p Secret123 -a Secret123 --domain-level=1 -U --setup-dns --forwarder 192.168.121.1 --auto-reverse 
echo Secret123 | kinit admin
ipa dnsrecord-add testrelm.test replica1.testrelm.test. --a-rec REPLICA1_IP
ipa dnsrecord-add testrelm.test replica2.testrelm.test. --a-rec REPLICA2_IP
ipa dnsconfig-mod --allow-sync-ptr=true

2. On replica1 execute:
ipa-client-install -U --domain testrelm.test --realm TESTRELM.TEST -p admin -w Secret123 --server master1.testrelm.test
echo Secret123 | kinit admin
ipa-replica-install -p Secret123 -w Secret123 -U --setup-ca --ip-address REPLICA1_IP -r TESTRELM.TEST 

3. On replica2 execute:
ipa-client-install -U --domain testrelm.test --realm TESTRELM.TEST -p admin -w Secret123 --server master1.testrelm.test
echo Secret123 | kinit admin
ipa-replica-install -p Secret123 -w Secret123 -U --setup-ca --ip-address REPLICA2_IP -r TESTRELM.TEST 

4. On master execute ipa topologysegment-find ca

Actual results:
------------------
2 segments matched
------------------
  Segment name: master1.testrelm.test-to-replica1.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: replica1.testrelm.test-to-replica2.testrelm.test
  Left node: replica1.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------

Expected results:
------------------
2 segments matched
------------------
  Segment name: master1.testrelm.test-to-replica1.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: master1.testrelm.test-to-replica2.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------


Additional info:
Output of "ipa topologysegment-find domain" is as expected:
------------------
2 segments matched
------------------
  Segment name: master1.testrelm.test-to-replica1.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: master1.testrelm.test-to-replica2.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------

On Fedora 28 (freeipa-server-4.7.2-1.1.fc28.x86_64) and on RHEL8.0 (ipa-server-4.7.1-11.module+el8+2842+7481110c.x86_64) I get expected result -- star topology for both ca and domain suffixes:

[root@master1 vagrant]# ipa topologysegment-find ca 
------------------
2 segments matched
------------------
  Segment name: master1.testrelm.test-to-replica1.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: master1.testrelm.test-to-replica2.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------

[root@master1 vagrant]# ipa topologysegment-find domain
------------------
2 segments matched
------------------
  Segment name: master1.testrelm.test-to-replica1.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: master1.testrelm.test-to-replica2.testrelm.test
  Left node: master1.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------
Comment 3 Florence Blanc-Renaud 2019-05-03 09:07:51 UTC 
Fixed upstream:
master:
https://pagure.io/freeipa/c/c0fd5e39c726ef4dc12e87a2f9c08ebb32ed27fe replica install: set the same master as preferred source for domain and CA
https://pagure.io/freeipa/c/52e5ef81a523f95fce9bd4c7ca87c0ca6b8ba8bf replica install: acknowledge ca_host override

ipa-4-7:
https://pagure.io/freeipa/c/745321469f00729231f5b8bf20958c0913eee5be replica install: acknowledge ca_host override

ipa-4-6:
https://pagure.io/freeipa/c/902606cede341851607cb8e648d09a2ded2616ab replica install: acknowledge ca_host override
Comment 4 Florence Blanc-Renaud 2019-05-03 09:09:49 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/7744
Comment 7 Mohammad Rizwan 2019-05-16 10:48:18 UTC 
version:
ipa-server-4.6.5-8.el7.x86_64

Steps:

Steps used as mentioned in description.

Actual result:

[root@master ~]# ipa topologysegment-find ca
------------------
2 segments matched
------------------
  Segment name: master.testrelm.test-to-replica1.testrelm.test
  Left node: master.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: master.testrelm.test-to-replica2.testrelm.test
  Left node: master.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------
[root@master ~]# 
[root@master ~]# ipa topologysegment-find domain
------------------
2 segments matched
------------------
  Segment name: master.testrelm.test-to-replica1.testrelm.test
  Left node: master.testrelm.test
  Right node: replica1.testrelm.test
  Connectivity: both

  Segment name: master.testrelm.test-to-replica2.testrelm.test
  Left node: master.testrelm.test
  Right node: replica2.testrelm.test
  Connectivity: both
----------------------------
Number of entries returned 2
----------------------------


Based on above observations, marking the bug as verified.
Comment 9 errata-xmlrpc 2019-08-06 13:09:37 UTC 
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://access.redhat.com/errata/RHBA-2019:2241
Note You need to log in before you can comment on or make changes to this bug.