Hide Forgot
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@pki-tomcat.service To restart the subsystem: systemctl restart pki-tomcatd@pki-tomcat.service 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@redhat.com> 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
QE Verification: Pretty obvious. Run pkispawn , no messages seen.
Test bits: ========== rpm -qa pki-* pki-tools-10.5.1-6.el7.x86_64 pki-ocsp-10.5.1-6.el7pki.noarch pki-javadoc-10.5.1-5.1.el7.noarch pki-base-10.5.1-6.el7.noarch pki-symkey-10.5.1-6.el7.x86_64 pki-server-10.5.1-6.el7.noarch pki-kra-10.5.1-6.el7.noarch pki-tks-10.5.1-6.el7pki.noarch pki-console-10.4.1-7.el7pki.noarch pki-core-debuginfo-10.5.1-5.1.el7pki.x86_64 pki-base-java-10.5.1-6.el7.noarch pki-ca-10.5.1-6.el7.noarch pki-tps-10.5.1-6.el7pki.x86_64 # rpm -qa jss* jss-4.4.0-11.el7.x86_64 # rpm -qa nss* nss-softokn-devel-3.34.0-2.el7.x86_64 nss-softokn-3.34.0-2.el7.x86_64 nss-3.34.0-4.el7.x86_64 nss-pem-1.0.3-4.el7.x86_64 nss-sysinit-3.34.0-4.el7.x86_64 nss-util-devel-3.34.0-2.el7.x86_64 nss-softokn-freebl-devel-3.34.0-2.el7.x86_64 nss-devel-3.34.0-4.el7.x86_64 nss-softokn-freebl-3.34.0-2.el7.x86_64 nss-util-3.34.0-2.el7.x86_64 nss-tools-3.34.0-4.el7.x86_64 Pkispawn installation with ExternalCA and CA doesn't show PR_FILE_NOT_FOUND_ERROR in above mentioned build. Moving to verified
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