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.
DescriptionAbhijeet Kasurde
2017-05-23 07:18:04 UTC
Description of problem:
IPA server installation fails due to pkispawn with following error
==========================================================================
INSTALLATION SUMMARY
==========================================================================
Administrator's username: admin
Administrator's PKCS #12 file:
/root/ca-agent.p12
Administrator's certificate nickname:
ipa-ca-agent
Administrator's certificate database:
/var/lib/ipa/tmp-lQulqs
2017-05-23T06:59:07Z DEBUG stderr=Notice: Trust flag u is set automatically if the private key is present.
Created symlink from /etc/systemd/system/multi-user.target.wants/pki-tomcatd.target to /usr/lib/systemd/system/pki-tomcatd.target.
Traceback (most recent call last):
File "/usr/sbin/pkispawn", line 838, in <module>
main(sys.argv)
File "/usr/sbin/pkispawn", line 579, in main
print_final_install_information(parser.mdict)
File "/usr/sbin/pkispawn", line 798, in print_final_install_information
if mdict['pki_fips_mode_enabled']:
KeyError: 'pki_fips_mode_enabled'
2017-05-23T06:59:07Z CRITICAL Failed to configure CA instance: Command '/usr/sbin/pkispawn -s CA -f /tmp/tmplJR0qR' returned non-zero exit status 1
2017-05-23T06:59:07Z CRITICAL See the installation logs and the following files/directories for more information:
2017-05-23T06:59:07Z CRITICAL /var/log/pki/pki-tomcat
[root@ipaserver01 ~]# rpm -qa ipa-server pki-server
pki-server-10.4.1-5.el7.noarch
ipa-server-4.5.0-13.el7.x86_64
[root@ipaserver01 ~]# cat /proc/sys/crypto/fips_enabled
0
[root@ipaserver01 ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 28
Version-Release number of selected component (if applicable):
pki-server-10.4.1-5.el7.noarch
ipa-server-4.5.0-13.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install IPA server without FIPS enabled mode with Pki-server version 10.4.1.5
Actual results:
IPA server installation fails due to pkispawn's keyerror
Expected results:
Installation should succeed
To fix this, we will simply always check for FIPS in the initialization scriptlet:
diff --git a/base/server/python/pki/server/deployment/scriptlets/initialization.py b/base/server/python/pki/server/deployment/scriptlets/initialization.py
index 0e31543..4dc4e9a 100644
--- a/base/server/python/pki/server/deployment/scriptlets/initialization.py
+++ b/base/server/python/pki/server/deployment/scriptlets/initialization.py
@@ -42,6 +42,8 @@ class PkiScriptlet(pkiscriptlet.AbstractBasePkiScriptlet):
# ALWAYS establish 'uid' and 'gid'
deployer.identity.set_uid(deployer.mdict['pki_user'])
deployer.identity.set_gid(deployer.mdict['pki_group'])
+ # ALWAYS check FIPS mode
+ deployer.fips.is_fips_enabled()
# ALWAYS initialize HSMs (when and if present)
deployer.hsm.initialize()
if config.str2bool(deployer.mdict['pki_skip_installation']):
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-2017:2110
Description of problem: IPA server installation fails due to pkispawn with following error ========================================================================== INSTALLATION SUMMARY ========================================================================== Administrator's username: admin Administrator's PKCS #12 file: /root/ca-agent.p12 Administrator's certificate nickname: ipa-ca-agent Administrator's certificate database: /var/lib/ipa/tmp-lQulqs 2017-05-23T06:59:07Z DEBUG stderr=Notice: Trust flag u is set automatically if the private key is present. Created symlink from /etc/systemd/system/multi-user.target.wants/pki-tomcatd.target to /usr/lib/systemd/system/pki-tomcatd.target. Traceback (most recent call last): File "/usr/sbin/pkispawn", line 838, in <module> main(sys.argv) File "/usr/sbin/pkispawn", line 579, in main print_final_install_information(parser.mdict) File "/usr/sbin/pkispawn", line 798, in print_final_install_information if mdict['pki_fips_mode_enabled']: KeyError: 'pki_fips_mode_enabled' 2017-05-23T06:59:07Z CRITICAL Failed to configure CA instance: Command '/usr/sbin/pkispawn -s CA -f /tmp/tmplJR0qR' returned non-zero exit status 1 2017-05-23T06:59:07Z CRITICAL See the installation logs and the following files/directories for more information: 2017-05-23T06:59:07Z CRITICAL /var/log/pki/pki-tomcat [root@ipaserver01 ~]# rpm -qa ipa-server pki-server pki-server-10.4.1-5.el7.noarch ipa-server-4.5.0-13.el7.x86_64 [root@ipaserver01 ~]# cat /proc/sys/crypto/fips_enabled 0 [root@ipaserver01 ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 28 Version-Release number of selected component (if applicable): pki-server-10.4.1-5.el7.noarch ipa-server-4.5.0-13.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install IPA server without FIPS enabled mode with Pki-server version 10.4.1.5 Actual results: IPA server installation fails due to pkispawn's keyerror Expected results: Installation should succeed