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.
Description of problem:
Running ipa-kra-install after ipa-server-install is failing:
[root@rhel7-1 ~]# ipa-kra-install -U -p Secret123
Starting new HTTPS connection (1): rhel7-1.example.com
===================================================================
This program will setup Dogtag KRA for the IPA Server.
Configuring KRA server (pki-tomcatd). Estimated time: 2 minutes
[1/10]: configuring KRA instance
Failed to configure KRA instance: Command '/usr/sbin/pkispawn -s KRA -f /tmp/tmpCKSAv2' returned non-zero exit status 1
See the installation logs and the following files/directories for more information:
/var/log/pki/pki-tomcat
[error] RuntimeError: KRA configuration failed.
Your system may be partly configured.
If you run into issues, you may have to re-install IPA on this server.
KRA configuration failed.
The ipa-kra-install command failed. See /var/log/ipaserver-kra-install.log for more information
Version-Release number of selected component (if applicable):
ipa-server-4.6.4-2.el7.x86_64
pki-kra-10.5.9-1.el7.noarch
How reproducible:
On my test VM, it's happening consistently.
Steps to Reproduce:
1. ipa-server-install -U --realm TESTRELM.TEST --domain testrelm.test --hostname rhel7-1.example.com --ip-address 192.168.122.71 --ds-password Secret123 --admin-password Secret123 --setup-dns --mkhomedir --ssh-trust-dns --no-dnssec-validation --allow-zone-overlap --reverse-zone=122.168.192.in-addr.arpa. --forwarder=192.168.122.1
2. ipa-kra-install -U -p Secret123
Actual results:
Fails as shown above.
Expected results:
No failure.
Additional info:
From ipa-kra-install.log:
Installing KRA into /var/lib/pki/pki-tomcat.
Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/kra/deployment.cfg.
Installation failed:
com.netscape.certsrv.base.PKIException: LDAP error (19): error result
Please check the KRA logs in /var/log/pki/pki-tomcat/kra.
2018-07-17T20:29:21Z DEBUG stderr=
2018-07-17T20:29:21Z CRITICAL Failed to configure KRA instance: Command '/usr/sbin/pkispawn -s KRA -f /tmp/tmpCKSAv2' returned non-zero exit status 1
2018-07-17T20:29:21Z CRITICAL See the installation logs and the following files/directories for more information:
2018-07-17T20:29:21Z CRITICAL /var/log/pki/pki-tomcat
From pki-tomcat/kra/debug:
[17/Jul/2018:15:29:21][http-bio-8443-exec-3]: === Admin Configuration ===
[17/Jul/2018:15:29:21][http-bio-8443-exec-3]: In LdapBoundConnFactory::getConn()
[17/Jul/2018:15:29:21][http-bio-8443-exec-3]: masterConn is connected: true
[17/Jul/2018:15:29:21][http-bio-8443-exec-3]: getConn: conn is connected true
[17/Jul/2018:15:29:21][http-bio-8443-exec-3]: getConn: mNumConns now 2
netscape.ldap.LDAPException: error result (19); pre-hashed passwords are not valid