1400421 – Replica install fails with old IPA master during pki instance creation

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 1400421 - Replica install fails with old IPA master during pki instance creation

Summary: Replica install fails with old IPA master during pki instance creation

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	pki-core
Sub Component:
Version:	6.9
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	RHCS Maintainers
QA Contact:	Asha Akkiangady
Docs Contact:
URL:
Whiteboard:
Duplicates (1):	1399405 (view as bug list)
Depends On:
Blocks:	1322059
TreeView+	depends on / blocked

Reported:	2016-12-01 08:01 UTC by Kaleem
Modified:	2017-03-21 11:59 UTC (History)
CC List:	5 users (show)
Fixed In Version:	pki-core-9.0.3-51.el6
Doc Type:	No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-03-21 11:59:37 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
pki-core-9.0.3-bz1400421.patch (3.44 KB, patch) 2016-12-01 18:24 UTC, Endi Sukma Dewata	no flags	Details \| Diff
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0802	0	normal	SHIPPED_LIVE	pki-core bug fix update	2017-03-21 12:51:24 UTC

Description Kaleem 2016-12-01 08:01:37 UTC

Description of problem:
Replica install on RHEL-7.3 update1 from 6.9 Master fails during pki instance creation.

Console output:
===============

   [42/42]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes 30 seconds
  [1/27]: creating certificate server user
  [2/27]: configuring certificate server instance
ipa.ipaserver.install.cainstance.CAInstance: CRITICAL Failed to configure CA instance: Command '/usr/sbin/pkispawn -s CA -f /tmp/tmp7tTBPF' returned non-zero exit status 1
ipa.ipaserver.install.cainstance.CAInstance: CRITICAL See the installation logs and the following files/directories for more information:
ipa.ipaserver.install.cainstance.CAInstance: CRITICAL   /var/log/pki/pki-tomcat
  [error] RuntimeError: CA configuration failed.
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

ipa.ipapython.install.cli.install_tool(Replica): ERROR    CA configuration failed.
ipa.ipapython.install.cli.install_tool(Replica): ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
[root@dhcp207-47 ~]#

Version-Release number of selected component (if applicable):
RHEL-6.9
--------
ipa-server-3.0.0-51.el6.x86_64
pki-ca-9.0.3-50.el6_8.noarch
[root@dhcp207-4 ~]# 

RHEL-7.3.update1
----------------
[root@dhcp207-47 ~]# rpm -q ipa-server pki-ca
ipa-server-4.4.0-14.el7_3.x86_64
pki-ca-10.3.3-14.el7_3.noarch
[root@dhcp207-47 ~]#

How reproducible:
Always

Steps to Reproduce:
1. Install IPA master on RHEL-6.9
2. Create replica gpg file for RHEL-7.3 update1 replica
3. Install replica on RHEL-7.3 update1

Actual results:
Replica installation fails

Expected results:
Replica installation should be successful

Comment 1 Kaleem 2016-12-01 08:02:46 UTC

For more details refer https://bugzilla.redhat.com/show_bug.cgi?id=1322059#c42

Comment 3 Endi Sukma Dewata 2016-12-01 18:24:20 UTC

Created attachment 1226967 [details]
pki-core-9.0.3-bz1400421.patch

This patch adds server hostname into token authentication request.

A test build is available at:
https://copr.devel.redhat.com/coprs/edewata/pki-rhel-6/build/6351/

The patch has shown to unblock IPA bug #1322059:
https://bugzilla.redhat.com/show_bug.cgi?id=1322059#c41

Comment 4 Endi Sukma Dewata 2016-12-01 19:44:55 UTC

Comment on attachment 1226967 [details]
pki-core-9.0.3-bz1400421.patch

Patch ACKed by alee (thanks!).

Comment 7 Petr Vobornik 2016-12-09 17:11:56 UTC

*** Bug 1399405 has been marked as a duplicate of this bug. ***

Comment 8 Xiyang Dong 2016-12-12 01:17:00 UTC

Verified on pki-core-9.0.3-51.el6:

Steps to verify:
1. Install IPA master on RHEL-6.9
[root@hp-ml350pgen8-01 ~]# ipactl status
Directory Service: RUNNING
KDC Service: RUNNING
KPASSWD Service: RUNNING
DNS Service: RUNNING
MEMCACHE Service: RUNNING
HTTP Service: RUNNING
CA Service: RUNNING
[root@hp-ml350pgen8-01 ~]# rpm -q ipa-server pki-ca
ipa-server-3.0.0-51.el6.x86_64
pki-ca-9.0.3-51.el6.noarch
2. Create replica gpg file for RHEL-7.3 update1 replica
[root@hp-ml350pgen8-01 ~]# ipa-replica-prepare $REPLICA
Directory Manager (existing master) password: 

Preparing replica for bkr-hv03-guest20.testrelm.test from hp-ml350pgen8-01.testrelm.test
Creating SSL certificate for the Directory Server
Creating SSL certificate for the dogtag Directory Server
Creating SSL certificate for the Web Server
Exporting RA certificate
Copying additional files
Finalizing configuration
Packaging replica information into /var/lib/ipa/replica-info-bkr-hv03-guest20.testrelm.test.gpg
[root@hp-ml350pgen8-01 ~]# scp /var/lib/ipa/replica-info-bkr-hv03-guest20.testrelm.test.gpg  root@$REPLICA:~
replica-info-bkr-hv03-guest20.testrelm.test.gpg                              100%   37KB  36.8KB/s   00:00 
3. Install replica on RHEL-7.3 update1
[root@bkr-hv03-guest20 ~]# rpm -q ipa-server pki-ca
ipa-server-4.4.0-14.el7_3.x86_64
pki-ca-10.3.3-14.el7_3.noarch
[root@bkr-hv03-guest20 ~]# ipa-replica-install --setup-dns --forwarder=$DNSFORWARD replica-info-bkr-hv03-guest20.testrelm.test.gpg
WARNING: conflicting time&date synchronization service 'chronyd' will
be disabled in favor of ntpd

Directory Manager (existing master) password: 

Checking DNS forwarders, please wait ...
Run connection check to master
admin password: 
Connection check OK
Adding [2620:52:0:1329:5054:ff:fe11:43ce bkr-hv03-guest20.testrelm.test] to your /etc/hosts file
Configuring NTP daemon (ntpd)
  [1/4]: stopping ntpd
  [2/4]: writing configuration
  [3/4]: configuring ntpd to start on boot
  [4/4]: starting ntpd
Done configuring NTP daemon (ntpd).
Configuring directory server (dirsrv). Estimated time: 1 minute
  [1/42]: creating directory server user
  [2/42]: creating directory server instance
  [3/42]: updating configuration in dse.ldif
  [4/42]: restarting directory server
  [5/42]: adding default schema
  [6/42]: enabling memberof plugin
  [7/42]: enabling winsync plugin
  [8/42]: configuring replication version plugin
  [9/42]: enabling IPA enrollment plugin
  [10/42]: enabling ldapi
  [11/42]: configuring uniqueness plugin
  [12/42]: configuring uuid plugin
  [13/42]: configuring modrdn plugin
  [14/42]: configuring DNS plugin
  [15/42]: enabling entryUSN plugin
  [16/42]: configuring lockout plugin
  [17/42]: configuring topology plugin
  [18/42]: creating indices
  [19/42]: enabling referential integrity plugin
  [20/42]: configuring ssl for ds instance
  [21/42]: configuring certmap.conf
  [22/42]: configure autobind for root
  [23/42]: configure new location for managed entries
  [24/42]: configure dirsrv ccache
  [25/42]: enabling SASL mapping fallback
  [26/42]: restarting directory server
  [27/42]: setting up initial replication
Starting replication, please wait until this has completed.
Update in progress, 2 seconds elapsed
Update succeeded

  [28/42]: adding sasl mappings to the directory
  [29/42]: updating schema
  [30/42]: setting Auto Member configuration
  [31/42]: enabling S4U2Proxy delegation
  [32/42]: importing CA certificates from LDAP
  [33/42]: initializing group membership
  [34/42]: adding master entry
  [35/42]: initializing domain level
  [36/42]: configuring Posix uid/gid generation
  [37/42]: adding replication acis
  [38/42]: enabling compatibility plugin
  [39/42]: activating sidgen plugin
  [40/42]: activating extdom plugin
  [41/42]: tuning directory server
  [42/42]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc). Estimated time: 30 seconds
  [1/7]: configuring KDC
  [2/7]: creating a keytab for the directory
  [3/7]: creating a keytab for the machine
  [4/7]: adding the password extension to the directory
  [5/7]: enable GSSAPI for replication
  [6/7]: starting the KDC
  [7/7]: configuring KDC to start on boot
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
  [1/2]: starting kadmin 
  [2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring ipa_memcached
  [1/2]: starting ipa_memcached 
  [2/2]: configuring ipa_memcached to start on boot
Done configuring ipa_memcached.
Configuring the web interface (httpd). Estimated time: 1 minute
  [1/20]: setting mod_nss port to 443
  [2/20]: setting mod_nss cipher suite
  [3/20]: setting mod_nss protocol list to TLSv1.0 - TLSv1.2
  [4/20]: setting mod_nss password file
  [5/20]: enabling mod_nss renegotiate
  [6/20]: adding URL rewriting rules
  [7/20]: configuring httpd
  [8/20]: configure certmonger for renewals
  [9/20]: setting up httpd keytab
  [10/20]: setting up ssl
  [11/20]: importing CA certificates from LDAP
  [12/20]: publish CA cert
  [13/20]: clean up any existing httpd ccache
  [14/20]: configuring SELinux for httpd
  [15/20]: create KDC proxy user
  [16/20]: create KDC proxy config
  [17/20]: enable KDC proxy
  [18/20]: restarting httpd
  [19/20]: configuring httpd to start on boot
  [20/20]: enabling oddjobd
Done configuring the web interface (httpd).
Configuring ipa-otpd
  [1/2]: starting ipa-otpd 
  [2/2]: configuring ipa-otpd to start on boot
Done configuring ipa-otpd.
Configuring ipa-custodia
  [1/5]: Generating ipa-custodia config file
  [2/5]: Making sure custodia container exists
  [3/5]: Generating ipa-custodia keys
  [4/5]: starting ipa-custodia 
  [5/5]: configuring ipa-custodia to start on boot
Done configuring ipa-custodia.
Applying LDAP updates
Upgrading IPA:
  [1/9]: stopping directory server
  [2/9]: saving configuration
  [3/9]: disabling listeners
  [4/9]: enabling DS global lock
  [5/9]: starting directory server
  [6/9]: upgrading server
  [7/9]: stopping directory server
  [8/9]: restoring configuration
  [9/9]: starting directory server
Done.
Restarting the directory server
Restarting the KDC
Configuring DNS (named)
  [1/8]: generating rndc key file
  [2/8]: setting up our own record
  [3/8]: adding NS record to the zones
  [4/8]: setting up kerberos principal
  [5/8]: setting up named.conf
  [6/8]: setting up server configuration
  [7/8]: configuring named to start on boot
  [8/8]: changing resolv.conf to point to ourselves
Done configuring DNS (named).
Configuring DNS key synchronization service (ipa-dnskeysyncd)
  [1/7]: checking status
  [2/7]: setting up bind-dyndb-ldap working directory
  [3/7]: setting up kerberos principal
  [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

Restarting the web server
Configuring client side components
Using existing certificate '/etc/ipa/ca.crt'.
Client hostname: bkr-hv03-guest20.testrelm.test
Realm: TESTRELM.TEST
DNS Domain: testrelm.test
IPA Server: bkr-hv03-guest20.testrelm.test
BaseDN: dc=testrelm,dc=test

Skipping synchronizing time with NTP server.
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
trying https://bkr-hv03-guest20.testrelm.test/ipa/json
Forwarding 'schema' to json server 'https://bkr-hv03-guest20.testrelm.test/ipa/json'
trying https://bkr-hv03-guest20.testrelm.test/ipa/session/json
Forwarding 'ping' to json server 'https://bkr-hv03-guest20.testrelm.test/ipa/session/json'
Forwarding 'ca_is_enabled' to json server 'https://bkr-hv03-guest20.testrelm.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
Forwarding 'host_mod' to json server 'https://bkr-hv03-guest20.testrelm.test/ipa/session/json'
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring testrelm.test as NIS domain.
Client configuration complete.

Comment 10 errata-xmlrpc 2017-03-21 11:59: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://rhn.redhat.com/errata/RHBA-2017-0802.html

Note You need to log in before you can comment on or make changes to this bug.