This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1693432 - [RFE] Using "LOCATIONS" within IPA, roipa-replica-install fails trying to contact wrong master
Summary: [RFE] Using "LOCATIONS" within IPA, roipa-replica-install fails trying to con...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
: 1693421 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 19:40 UTC by kludhwan
Modified: 2024-01-17 04:25 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 17:51:48 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7639 0 None None None 2021-12-16 12:36:08 UTC
Red Hat Issue Tracker   RHEL-4817 0 None Migrated None 2023-09-18 17:48:33 UTC
Red Hat Knowledge Base (Solution) 4094761 0 Configure None ipa-replica-install picks wrong replica for CA initial replication 2019-04-30 10:17:33 UTC

Description kludhwan 2019-03-27 19:40:10 UTC 
2 LOCATIONS defined in IPA, DEV and PROD. 3 current IPA servers - 2 in PROD and 1 in DEV. They are in distinct subnets and firewall off except the masters can talk. When tryin to add a 4th replica in DEV, it fails with 2 issues listed in detail below - both having to do with LOCATIONS feature.

[root@IPA1 ~]# ipa-replica-install --setup-dns --no-forwarders --setup-ca
ipaserver.install.server.replicainstall: ERROR    Could not resolve hostname IPA1.example.com using DNS. Clients may not function properly. Please check your DNS setup. (Note that this check queries IPA DNS directly and ignores /etc/hosts.)
Continue? [no]: 
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

ipa2ython.admintool: ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information

and review the log (attached ) you will see it is trying to contact ipa2 which is 10.1.x.x and located in PROD location. DEV location is defined as 10.0 network. 

In the second example, the option of --no-host-dns is used to stop the lookup, but instead it fails later as it tries to contact the LDAP server, but again, in PROD and NOT DEV. It is as though the locations are reversed.

These are locations as defined: 
[root@IPA1 ~]# ipa server-show IPA1.example.com (IP = 10.0.x.X)
  Server name: IPA1.example.com
  Managed suffixes: domain, ca
  Min domain level: 0
  Max domain level: 1
  Location: DEV
  Enabled server roles: CA server, IPA master, DNS server, NTP server

[root@IPA1 ~]# ipa server-show ipa2.example.com (IP = 10.1.x.x)
  Server name: ipa2.example.com
  Managed suffixes: domain, ca
  Min domain level: 0
  Max domain level: 1
  Location: PROD
  Enabled server roles: CA server, IPA master, DNS server, NTP server

[root@IPA1 ~]# ipa server-show ipa3.example.com (IP = 10.1.x.x)
  Server name: ipa3.example.com
  Managed suffixes: domain
  Min domain level: 0
  Max domain level: 1
  Location: PROD
  Enabled server roles: IPA master, DNS server, NTP server


overall current layout

ipa3 <---> ipa2 <--- | ---> IPA1 <---> (trying to create) IPA1 
                                          ^
                                   Firewall allowing ony IPA servers to talk

Once IPA1 is created it  will be connected to another outside replica then back to ipa3 to complete the ring.
Comment 2 kludhwan 2019-03-27 19:41:06 UTC 

*** This bug has been marked as a duplicate of bug 1693421 ***
Comment 3 kludhwan 2019-03-27 19:43:10 UTC 
*** Bug 1693421 has been marked as a duplicate of this bug. ***
Comment 6 François Cami 2019-03-29 16:32:14 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/7744
Comment 9 François Cami 2019-03-29 19:01:18 UTC 
Fixed upstream:
master:
https://pagure.io/freeipa/c/c0fd5e39c726ef4dc12e87a2f9c08ebb32ed27fe
https://pagure.io/freeipa/c/52e5ef81a523f95fce9bd4c7ca87c0ca6b8ba8bf
Comment 10 François Cami 2019-03-29 19:01:56 UTC 
Fixed upstream:
ipa-4-7:
https://pagure.io/freeipa/c/745321469f00729231f5b8bf20958c0913eee5be
Comment 11 François Cami 2019-03-29 19:02:21 UTC 
Fixed upstream:
ipa-4-6:
https://pagure.io/freeipa/c/902606cede341851607cb8e648d09a2ded2616ab
Comment 12 François Cami 2019-04-01 11:33:18 UTC 
Moving to RHEL8.
Setting back to ASSIGNED as installing a location-specific replica is a valid RFE.
Comment 19 RHEL Program Management 2023-09-18 17:46:49 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 20 RHEL Program Management 2023-09-18 17:51:48 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 21 Red Hat Bugzilla 2024-01-17 04:25:02 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.