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.
Bug 1520277 - PR_FILE_NOT_FOUND_ERROR during pkispawn
Summary: PR_FILE_NOT_FOUND_ERROR during pkispawn
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Ade Lee
QA Contact: Asha Akkiangady
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-04 07:49 UTC by Geetika Kapoor
Modified: 2020-10-04 21:38 UTC (History)
3 users (show)

Fixed In Version: pki-core-10.5.1-6.el7
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2018-04-10 17:02:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2991 0 None None None 2020-10-04 21:38:26 UTC
Red Hat Product Errata RHBA-2018:0925 0 None None None 2018-04-10 17:03:37 UTC

Description Geetika Kapoor 2017-12-04 07:49:53 UTC 
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:
Comment 3 Ade Lee 2018-01-12 18:49:43 UTC 
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
Comment 5 Ade Lee 2018-01-26 16:12:15 UTC 
QE Verification:

Pretty obvious.  Run pkispawn , no messages seen.
Comment 6 Geetika Kapoor 2018-01-30 19:44:52 UTC 
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
Comment 10 errata-xmlrpc 2018-04-10 17:02:54 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.