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 1623679 - Installation of replica against a specific master [rhel-7.5.z]
Summary: Installation of replica against a specific master [rhel-7.5.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Michal Reznik
URL:
Whiteboard:
Depends On: 1591824
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-29 20:58 UTC by Jaroslav Reznik
Modified: 2021-09-09 15:26 UTC (History)
10 users (show)

Fixed In Version: ipa-4.5.4-10.el7_5.4.2
Doc Type: Bug Fix
Doc Text:
Cause: The various steps of a replica installation do not consistently use the same master and may end up trying to read data that has not been replicated yet. Consequence: Installation of a replica may fail due to race conditions when multiple masters are available. Fix: Improve the replica installation by ensuring that the same master is consistently used by all the steps Result: Replica installation is successful even when multiple masters are available.
Clone Of: 1591824
Environment:
Last Closed: 2018-09-25 19:07:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2760 0 None None None 2018-09-25 19:08:06 UTC

Description Jaroslav Reznik 2018-08-29 20:58:16 UTC 
This bug has been copied from bug #1591824 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 3 Michal Reznik 2018-09-11 16:08:05 UTC 
Verified on:

version:
ipa-server-4.5.4-10.el7_5.4.4.x86_64

Steps:
1) Install master with CA
2) Install replica1 without CA
3) Stop ipa-custodia on replica1
   $  systemctl stop ipa-custodia.service
4) Install replica2 from replica1. Since replica1 doesn't have a CA, the installer on replica2 will fetch all secrets from master.

Actual result:

replica2 installed successfully from replica1.

Master - vm-171-027
~~~~~~

[root@vm-171-027 ~]# tail -1f /var/log/ipaserver-install.log 
2018-09-11T15:28:55Z INFO The ipa-server-install command was successful

Replica1 - vm-189
~~~~~~~~

[root@vm-189 ~]# tail -1f /var/log/ipareplica-install.log
2018-09-11T15:36:38Z INFO The ipa-replica-install command was successful
^C
[root@vm-189 ~]# 
[root@vm-189 ~]# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
httpd Service: RUNNING
ipa-custodia Service: STOPPED
ntpd Service: RUNNING
ipa-otpd Service: RUNNING
ipa: INFO: The ipactl command was successful
[root@vm-189 ~]# 


Replica2 - vm-057
~~~~~~~~

[root@vm-057 ~]# ipa-replica-install -U --setup-dns --forwarder 10.37.170.1 --no-reverse --setup-ca --server vm-189.ipa.test --domain IPA.TEST --admin-password Secret123 --principal admin
WARNING: conflicting time&date synchronization service 'chronyd' will
be disabled in favor of ntpd

Configuring client side components
Client hostname: vm-057.ipa.test
Realm: IPA.TEST
DNS Domain: IPA.TEST
IPA Server: vm-189.ipa.test
BaseDN: dc=dom-171-027,dc=ipa,dc=test

Skipping synchronizing time with NTP server.
Successfully retrieved CA cert
    Subject:     CN=Certificate Authority,O=IPA.TEST
    Issuer:      CN=Certificate Authority,O=IPA.TEST
    Valid From:  2018-09-11 15:24:07
    Valid Until: 2038-09-11 15:24:07

Enrolled in IPA realm IPA.TEST
Created /etc/ipa/default.conf
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
Configured /etc/krb5.conf for IPA realm IPA.TEST
trying https://vm-189.ipa.test/ipa/json
[try 1]: Forwarding 'schema' to json server 'https://vm-189.ipa.test/ipa/json'
trying https://vm-189.ipa.test/ipa/session/json
[try 1]: Forwarding 'ping' to json server 'https://vm-189.ipa.test/ipa/session/json'
[try 1]: Forwarding 'ca_is_enabled' to json server 'https://vm-189.ipa.test/ipa/session/json'
Systemwide CA database updated.
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
[try 1]: Forwarding 'host_mod' to json server 'https://vm-189.ipa.test/ipa/session/json'
Could not update DNS SSHFP records.
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring IPA.TEST as NIS domain.
Client configuration complete.
The ipa-client-install command was successful

Checking DNS forwarders, please wait ...
Run connection check to master
Connection check OK
Configuring NTP daemon (ntpd)
  [1/4]: stopping ntpd
  [2/4]: writing configuration
  [3/4]: configuring ntpd to start on boot
...
...
...
  [4/7]: setting up SoftHSM
  [5/7]: adding DNSSEC containers
  [6/7]: creating replica keys
  [7/7]: configuring ipa-dnskeysyncd to start on boot
Done configuring DNS key synchronization service (ipa-dnskeysyncd).
Restarting ipa-dnskeysyncd
Restarting named
Updating DNS system records

Global DNS configuration in LDAP server is empty
You can use 'dnsconfig-mod' command to set global DNS options that
would override settings in local named.conf files

[root@vm-057 ~]# 
[root@vm-057 ~]# ipa server-role-find
-----------------------
18 server roles matched
-----------------------
  Server name: vm-057.ipa.test
  Role name: CA server
  Role status: enabled

  Server name: vm-171-027.ipa.test
  Role name: CA server
  Role status: enabled

  Server name: vm-189.ipa.test
  Role name: CA server
  Role status: absent

  Server name: vm-057.ipa.test
  Role name: DNS server
  Role status: enabled

  Server name: vm-171-027.ipa.test
  Role name: DNS server
  Role status: enabled

  Server name: vm-189.ipa.test
  Role name: DNS server
  Role status: absent

  Server name: vm-057.ipa.test
  Role name: NTP server
  Role status: enabled

  Server name: vm-171-027.ipa.test
  Role name: NTP server
  Role status: enabled

  Server name: vm-189.ipa.test
  Role name: NTP server
  Role status: enabled

  Server name: vm-057.ipa.test
  Role name: AD trust agent
  Role status: absent

  Server name: vm-171-027.ipa.test
  Role name: AD trust agent
  Role status: absent

  Server name: vm-189.ipa.test
  Role name: AD trust agent
  Role status: absent

  Server name: vm-057.ipa.test
  Role name: KRA server
  Role status: absent

  Server name: vm-171-027.ipa.test
  Role name: KRA server
  Role status: absent

  Server name: vm-189.ipa.test
  Role name: KRA server
  Role status: absent

  Server name: vm-057.ipa.test
  Role name: AD trust controller
  Role status: absent

  Server name: vm-171-027.ipa.test
  Role name: AD trust controller
  Role status: absent

  Server name: vm-189.ipa.test
  Role name: AD trust controller
  Role status: absent
-----------------------------
Number of entries returned 18
-----------------------------
[root@vm-057 ~]#
Comment 5 errata-xmlrpc 2018-09-25 19:07:13 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-2018:2760
Note You need to log in before you can comment on or make changes to this bug.