#2701 Unable to install IPA server due to pkispawn error
Closed: fixed Opened by mharmsen.

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
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 ~]# 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

Steps to Reproduce:

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

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: blocker

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1454603

Metadata Update from @mharmsen:
- Issue assigned to mharmsen

Metadata Update from @mharmsen:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.4.5 (was: 10.4)
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2821

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata