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.
The *pkispawn* utility no longer displays incorrect errors
Previously, during a successful installation of Certificate System, the *pkispawn* utility incorrectly displayed errors related to deleting temporary certificates. The problem has been fixed, and the error messages no longer display if the installation succeeds.
Description of problem:
During pkispawn, we see below message in stderr:
certutil: Could not find cert: Server-Cert cert-topology-02-CA
: PR_FILE_NOT_FOUND_ERROR: File not found
Installation is successful. Looks like cosmetic fix but this might confuse any user.
Installation logs:
==================
Log file: /var/log/pki/pki-ca-spawn.20171121154949.log
Installing CA into /var/lib/pki/pki-tomcat.
Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/ca/deployment.cfg.
certutil: Could not find cert: Server-Cert cert-pki-tomcat
: PR_FILE_NOT_FOUND_ERROR: File not found
Notice: Trust flag u is set automatically if the private key is present.
==========================================================================
INSTALLATION SUMMARY
==========================================================================
Administrator's username: caadmin
Administrator's PKCS #12 file:
/root/.dogtag/pki-tomcat/ca_admin_cert.p12
To check the status of the subsystem:
systemctl status pki-tomcatd
To restart the subsystem:
systemctl restart pki-tomcatd
The URL for the subsystem is:
https://pki1.example.com:8443/ca
PKI instances will be enabled upon system boot
==========================================================================
Version-Release number of selected component (if applicable):
10.5
How reproducible:
always during pkispawn installation
Steps to Reproduce:
1.Do pkispawn and check installation logs.
2.
3.
Actual results:
Expected results:
Additional info:
10.5:
Commit 2e5f4408a09819242de0b1b0eb023e5ddf074acd (HEAD -> fix_spurious_messages_10.5)
Author: Ade Lee <alee>
Date: Thu Jan 11 15:16:02 2018 -0500
Modify get_cert to get rid of spurious certutil error messages
Also shortened some lines to comply with PEP8
rhbz# 1520277
Change-Id: I71d5ecb24c979c1be642a0c3529aebfae6e98aa7
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, 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/RHBA-2018:0925
Description of problem: During pkispawn, we see below message in stderr: certutil: Could not find cert: Server-Cert cert-topology-02-CA : PR_FILE_NOT_FOUND_ERROR: File not found Installation is successful. Looks like cosmetic fix but this might confuse any user. Installation logs: ================== Log file: /var/log/pki/pki-ca-spawn.20171121154949.log Installing CA into /var/lib/pki/pki-tomcat. Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/ca/deployment.cfg. certutil: Could not find cert: Server-Cert cert-pki-tomcat : PR_FILE_NOT_FOUND_ERROR: File not found Notice: Trust flag u is set automatically if the private key is present. ========================================================================== INSTALLATION SUMMARY ========================================================================== Administrator's username: caadmin Administrator's PKCS #12 file: /root/.dogtag/pki-tomcat/ca_admin_cert.p12 To check the status of the subsystem: systemctl status pki-tomcatd To restart the subsystem: systemctl restart pki-tomcatd The URL for the subsystem is: https://pki1.example.com:8443/ca PKI instances will be enabled upon system boot ========================================================================== Version-Release number of selected component (if applicable): 10.5 How reproducible: always during pkispawn installation Steps to Reproduce: 1.Do pkispawn and check installation logs. 2. 3. Actual results: Expected results: Additional info: