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:
Bad jss4.jar symlink crashes IPA server installation:
# ipa-server-install
...
[35/37]: enabling compatibility plugin
[36/37]: tuning directory server
[37/37]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring certificate server (pki-tomcatd): Estimated time 3 minutes 30 seconds
[1/20]: creating certificate server user
[2/20]: configuring certificate server instance
ipa : CRITICAL failed to configure ca instance Command '/usr/sbin/pkispawn -s CA -f /tmp/tmp6L6j03' returned non-zero exit status 1
Configuration of CA failed
/var/log/ipaserver-install.log
2013-06-14T11:19:00Z DEBUG Starting external process
2013-06-14T11:19:00Z DEBUG args=/usr/sbin/pkispawn -s CA -f /tmp/tmp6L6j03
2013-06-14T11:19:04Z DEBUG Process finished, return code=1
2013-06-14T11:19:04Z DEBUG stdout=Loading deployment configuration from /tmp/tmp6L6j03.
Installing CA into /var/lib/pki/pki-tomcat.
Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/ca/deployment.cfg.
Installation failed.
2013-06-14T11:19:04Z DEBUG stderr=pkispawn : WARNING ....... Dangling symlink '/var/lib/pki/pki- tomcat/common/lib/jss4.jar'-->'/usr/lib64/java/jss4.jar'
2013-06-14T11:19:04Z CRITICAL failed to configure ca instance Command '/usr/sbin/pkispawn -s CA -f /tmp/tmp6L6j03' returned non-zero exit status 1
Version-Release number of selected component (if applicable):
ipa-server-3.2.1-1.el7.x86_64
pki-ca-10.0.3-1.el7.noarch
How reproducible:
Steps to Reproduce:
1. Run ipa-server-install
2.
3.
Actual results:
pki-ca installation crashes
Expected results:
pki-ca installation does not crash
Additional info:
The actual file seems to be here: /usr/lib64/jss/jss4.jar
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.