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.
Created attachment 1757198[details]
ipa server install , ds error , ca debug log combined in one file.
Description of problem:
PKI instance creation failed with following error message
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes
[1/28]: configuring certificate server instance
Failed to configure CA instance: CalledProcessError(Command ['/usr/sbin/pkispawn', '-s', 'CA', '-f', '/tmp/tmpznto2c35', '--debug'] returned non-zero exit status 1: 'INFO: Connecting to LDAP server at ldap://ci-vm-10-0-102-13.testrealm.test:389\nINFO: Connecting to LDAP server at ldap://ci-vm-10-0-102-13.testrealm.test:389\nDEBUG: Installing Maven dependencies:
....
.......
....
See the installation logs and the following files/directories for more information:
/var/log/pki/pki-tomcat
[error] RuntimeError: CA configuration failed.
CA configuration failed.
Version-Release number of selected component (if applicable):
[root@ci-vm-10-0-102-13 ca]# rpm -q ipa-server 389-ds-base pki-ca
ipa-server-4.9.2-1.module+el8.4.0+9973+3d202164.x86_64
389-ds-base-1.4.3.16-10.module+el8.4.0+9902+6195a65d.x86_64
pki-ca-10.10.4-1.module+el8.4.0+9861+7cddd5b6.noarch
[root@ci-vm-10-0-102-13 ca]#
How reproducible:
Always
Steps to Reproduce:
1. Install IPA server with latest nightly compose
Actual results:
PKI instance creation fails during IPA install
Expected results:
PKI instance creation should be successful during IPA install
Additional info:
Please find the attached log files (ipa-server-install.log, erros log from dirsrv, ca debug logs)
Checkins:
v10.10:
commit 21735b429228bef5e4d56ad154685d4942e9fe25 (HEAD -> v10.10, origin/v10.10)
Author: jmagne <jmagne>
Date: Mon Feb 22 13:44:20 2021 -0800
pkispawn fails against 389-ds 1.4.3.19 #3458 (#3465)
Add suggested patch from stanislavlevin to solve this issue.
Also add f34 to the ipa tests,this time really add the tests.
Upon further review, back out of f34 tests until the infractructure
supports it.
Also hardcode tomcat app setting in spec file for the moment to
avoid possible glitches on certain platform.
Co-authored-by: Jack Magne <jmagne>
master:
commit 48778b2f63cd6d7d4372eeb6b87570c23d862e46 (HEAD -> master, origin/master, origin/HEAD)
Author: jmagne <jmagne>
Date: Mon Feb 22 13:44:20 2021 -0800
pkispawn fails against 389-ds 1.4.3.19 #3458 (#3465)
Add suggested patch from stanislavlevin to solve this issue.
Also add f34 to the ipa tests,this time really add the tests.
Upon further review, back out of f34 tests until the infractructure
supports it.
Also hardcode tomcat app setting in spec file for the moment to
avoid possible glitches on certain platform.
Co-authored-by: Jack Magne <jmagne>
Marking POST:
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 (Moderate: pki-core:10.6 and pki-deps:10.6 security, bug fix, and enhancement update), 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/RHSA-2021:1775
Created attachment 1757198 [details] ipa server install , ds error , ca debug log combined in one file. Description of problem: PKI instance creation failed with following error message Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes [1/28]: configuring certificate server instance Failed to configure CA instance: CalledProcessError(Command ['/usr/sbin/pkispawn', '-s', 'CA', '-f', '/tmp/tmpznto2c35', '--debug'] returned non-zero exit status 1: 'INFO: Connecting to LDAP server at ldap://ci-vm-10-0-102-13.testrealm.test:389\nINFO: Connecting to LDAP server at ldap://ci-vm-10-0-102-13.testrealm.test:389\nDEBUG: Installing Maven dependencies: .... ....... .... See the installation logs and the following files/directories for more information: /var/log/pki/pki-tomcat [error] RuntimeError: CA configuration failed. CA configuration failed. Version-Release number of selected component (if applicable): [root@ci-vm-10-0-102-13 ca]# rpm -q ipa-server 389-ds-base pki-ca ipa-server-4.9.2-1.module+el8.4.0+9973+3d202164.x86_64 389-ds-base-1.4.3.16-10.module+el8.4.0+9902+6195a65d.x86_64 pki-ca-10.10.4-1.module+el8.4.0+9861+7cddd5b6.noarch [root@ci-vm-10-0-102-13 ca]# How reproducible: Always Steps to Reproduce: 1. Install IPA server with latest nightly compose Actual results: PKI instance creation fails during IPA install Expected results: PKI instance creation should be successful during IPA install Additional info: Please find the attached log files (ipa-server-install.log, erros log from dirsrv, ca debug logs)