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.
I am not sure if you guys are already on top of this but we've been seeing that freeipa cannot be installed on centos 9 with jss-5.2.0-0.2.beta1.el9.
This is the osp/tripleo related issue: https://bugs.launchpad.net/tripleo/+bug/1969613
INFO: Creating new security domain
INFO: Using CA at https://freeipa-0.bgp.ftw:443
INFO: Storing subsystem config: /var/lib/pki/pki-tomcat/ca/conf/CS.cfg
INFO: Storing registry config: /var/lib/pki/pki-tomcat/ca/conf/registry.cfg
INFO: Removing existing database
DEBUG: Command: /usr/sbin/runuser -u pkiuser -- /usr/lib/jvm/jre-11-openjdk/bin/java -classpath /usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/tomcat-servlet-api.jar:/usr/share/pki/ca/webapps/ca/WEB-INF/lib/*:/var/lib/pki/pki-tomcat/common/lib/*:/usr/share/pki/lib/* -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Dcatalina.base=/var/lib/pki/pki-tomcat -Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/lib/pki/pki-tomcat/temp -Djava.util.logging.config.file=/etc/pki/pki-tomcat/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dcom.redhat.fips=false org.dogtagpki.server.cli.PKIServerCLI ca-db-remove --force --debug
InvocationTargetException: null
CalledProcessError: Command '['/usr/sbin/runuser', '-u', 'pkiuser', '--', '/usr/lib/jvm/jre-11-openjdk/bin/java', '-classpath', '/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/tomcat-servlet-api.jar:/usr/share/pki/ca/webapps/ca/WEB-INF/lib/*:/var/lib/pki/pki-tomcat/common/lib/*:/usr/share/pki/lib/*', '-Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory', '-Dcatalina.base=/var/lib/pki/pki-tomcat', '-Dcatalina.home=/usr/share/tomcat', '-Djava.endorsed.dirs=', '-Djava.io.tmpdir=/var/lib/pki/pki-tomcat/temp', '-Djava.util.logging.config.file=/etc/pki/pki-tomcat/logging.properties', '-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager', '-Dcom.redhat.fips=false', 'org.dogtagpki.server.cli.PKIServerCLI', 'ca-db-remove', '--force', '--debug']' returned non-zero exit status 255.
File "/usr/lib/python3.9/site-packages/pki/server/pkispawn.py", line 585, in main
scriptlet.spawn(deployer)
File "/usr/lib/python3.9/site-packages/pki/server/deployment/scriptlets/configuration.py", line 594, in spawn
subsystem.remove_database(force=True)
File "/usr/lib/python3.9/site-packages/pki/server/subsystem.py", line 1028, in remove_database
self.run(cmd, as_current_user=as_current_user)
File "/usr/lib/python3.9/site-packages/pki/server/subsystem.py", line 1650, in run
return subprocess.run(
File "/usr/lib64/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
2022-04-20T10:30:27Z CRITICAL Failed to configure CA instance
2022-04-20T10:30:27Z CRITICAL See the installation logs and the following files/directories for more information:
2022-04-20T10:30:27Z CRITICAL /var/log/pki/pki-tomcat
2022-04-20T10:30:27Z DEBUG Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/ipaserver/install/service.py", line 635, in start_creation
run_step(full_msg, method)
File "/usr/lib/python3.9/site-packages/ipaserver/install/service.py", line 621, in run_step
method()
File "/usr/lib/python3.9/site-packages/ipaserver/install/cainstance.py", line 626, in __spawn_instance
DogtagInstance.spawn_instance(
File "/usr/lib/python3.9/site-packages/ipaserver/install/dogtaginstance.py", line 227, in spawn_instance
self.handle_setup_error(e)
File "/usr/lib/python3.9/site-packages/ipaserver/install/dogtaginstance.py", line 594, in handle_setup_error
raise RuntimeError(
RuntimeError: CA configuration failed.
2022-04-20T10:30:27Z DEBUG [error] RuntimeError: CA configuration failed.
We resorted to downgrading jss to 5.0 for now.
There are additional logs attached to that launchpad bug if you want to check the full trace.
Comment 1Endi Sukma Dewata
2022-04-22 17:00:24 UTC
Hi, we're in the process of updating pki-core and its dependencies
(including jss) in RHEL 9.1 (not RHEL 9.0) which is covered by bug
#2075154. The process was interrupted due to some gating issues,
but the issues have be resolved/waived so the bug is now ON_QA.
I'm not sure how the release process works in CentOS, but keep in
mind that the RHEL 9.1 packages that we have now have not been
fully tested by QE (thus the beta version designation). If this is
a concern I'd suggest to stay with the packages that correspond to
RHEL 9.0 until RHEL 9.1 is officially released.
*** This bug has been marked as a duplicate of bug 2075154 ***