gkapoor made the following observation:
During pkispawn, we see below message in stderr:
Installation is successful. Looks like cosmetic fix but this might confuse any user.
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
==========================================================================
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1520277 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue assigned to edewata
Metadata Update from @vakwetu: - Issue assigned to vakwetu (was: edewata)
master:
commit 52a7543e6f8ac4728caa9eeaa933080c2262af05 (origin/master, origin/HEAD, gerrit/master, master) 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
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
Metadata Update from @vakwetu: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.4 (was: 10.5)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.4-1.fc27
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2991
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Log in to comment on this ticket.